| 3 | Approval of the Agenda | |
|---|---|---|
| R3-237001 | RAN3#122 Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-237002 | RAN3#121-bis Meeting Report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-237003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| 7 | General, protocol principles and issues | |
| R3-237004 | TR 30.531 v1.49.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-237522 | Discussion on general RAN3 principles on support of peer node capabilities between NG-RAN and CN | Ericsson, LGE, Vodafone |
| 8.1 | New Incoming LSs | |
| R3-237135 | LS Out Sub One Second Report Period for Deferred Location over SBI | CT4(Ericsson) |
| R3-237137 | LS on Rel-18 higher-layers parameter list | RAN1(Ericsson) |
| R3-237153 | Reply LS on RedCap UE MBS Broadcast reception | SA2(ZTE) |
| R3-237155 | LS on AI/ML Core Network enhancements | SA2(Qualcomm) |
| R3-237165 | LS on NAS Cause Value - Unspecified | SA3-LI(Trideaworks) |
| R3-237169 | Discussion on SA2 LS on RedCap UE MBS Broadcast reception | ZTE, Lenovo, CATT, Qualcomm, CBN |
| R3-237192 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-237221 | Discussion on the LS from SA2 on RedCap UE MBS Broadcast reception | Huawei, CBN |
| R3-237222 | [draft] Reply LS to R3-237153 (S2-2311706) on RedCap UE MBS Broadcast reception | Huawei |
| R3-237223 | Introduction of RedCap UE Information for MBS Broadcast reception [MBS Broadcast RedCap] | Huawei, CBN |
| R3-237224 | Introduction of RedCap UE Information for MBS Broadcast reception [MBS Broadcast RedCap] | Huawei, CBN |
| R3-237265 | Indication of MBS Broadcast Session for Redcap UEs | Nokia, Nokia Shanghai Bell |
| R3-237266 | Response LS on RedCap UE MBS Broadcast Reception | Nokia, Nokia Shanghai Bell |
| R3-237267 | Indication of Redcap delivery for Broadcast Sessions [Redcap] | Nokia, Nokia Shanghai Bell |
| R3-237268 | Indication of Redcap delivery for Broadcast Sessions [Redcap] | Nokia, Nokia Shanghai Bell |
| R3-237329 | Discussion on AI/ML Core Network Enhancement | Samsung |
| R3-237330 | [Draft] Reply LS on AI/ML Core Network Enhancements | Samsung |
| R3-237344 | Consideration on the LS from SA2 on AI/ML enhancement | ZTE |
| R3-237345 | [DRAFT] Reply to LS on AI/ML Core Network enhancements | ZTE |
| R3-237346 | Discussion on the LS from CT4 on finer periodicity | ZTE |
| R3-237347 | Correction to NRPPa on missing finer periodicity | ZTE |
| R3-237348 | Correction to F1AP on missing finer periodicity | ZTE |
| R3-237376 | Discussion on R3-237155 (S2-2311921) on LS on AI/ML Core Network enhancements | Huawei |
| R3-237377 | [Draft] Reply to R3-237155 (S2-2311921) on LS on AI/ML Core Network enhancements | Huawei |
| R3-237393 | Discussion on SA2 LS about SA impacts for R19 RAN AI/ML | Xiaomi |
| R3-237395 | On the reply LS from SA2 for RedCap UE MBS Broadcast reception | Ericsson |
| R3-237489 | Discussions about LS from SA2 | Ericsson, AT&T, InterDigital |
| R3-237490 | Reply LS on AI/ML Core Network enhancements | Ericsson, AT&T, InterDigital |
| R3-237517 | Correction on Cause Meaning in NGAP | Ericsson |
| R3-237518 | Draft LS on NAS Cause Value - Unspecified | Ericsson |
| R3-237523 | Support of Sub One Second Report Interval following CT4 LS | Ericsson |
| R3-237524 | Addition of milliseconds value to UE reporting Interval | Ericsson |
| R3-237550 | NAS Cause Value - Unspecified | Huawei |
| R3-237551 | [draft] Reply to R3-237165/s3i230621 on NAS Cause Value - Unspecified | Huawei |
| R3-237552 | Correction of Cause Value - Unspecified | Huawei |
| R3-237553 | Correction of Cause Value - Unspecified | Huawei |
| R3-237554 | Correction of Cause Value - Unspecified | Huawei |
| R3-237555 | Correction of Cause Value - Unspecified | Huawei |
| R3-237559 | Discussion on reply LS on coordination between NWDAF and NG-RAN | CATT,Deutsche Telekom |
| R3-237574 | Discussion related to the incoming LS from SA2 on the support of AI/ML for air interface and NG-RAN in RAN | Nokia, Nokia Shanghai Bell |
| R3-237575 | [Draft] Response LS to SA2 LS on AI/ML Core Network enhancements | Nokia, Nokia Shanghai Bell |
| R3-237693 | (CR to TS 38.413) Introduction of RedCap UE MBS Broadcast reception | ZTE, Lenovo, CATT, Qualcomm, CBN |
| R3-237694 | (CR to TS 38.473) Introduction of RedCap UE MBS Broadcast reception | ZTE |
| R3-237695 | Draft Reply LS to SA2 on RedCap UE MBS Broadcast reception | ZTE |
| R3-237701 | (CR to TS 38.413) Introduction of RedCap UE MBS Broadcast reception | ZTE, Lenovo, CATT, Qualcomm, CBN |
| R3-237732 | Response to R3-237550 | ZTE Corporation |
| R3-237741 | CB:1_ReportPeriod | Ericsson |
| R3-237742 | CB:#2_NASCauseVAlue | Nokia |
| R3-237743 | CB:#3_RedcapMBS | ZTE |
| R3-237745 | Reply to LS on AI/ML Core Network enhancements | RAN3(ZTE) |
| R3-237811 | Indication of Redcap delivery for Broadcast Sessions [Redcap] | Nokia, Nokia Shanghai Bell |
| R3-237900 | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | ZTE, Lenovo, CATT, Qualcomm, CBN, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237901 | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | Huawei, CBN, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237902 | Reply LS to SA2 on RedCap UE MBS Broadcast reception | ZTE |
| R3-237955 | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | Huawei, CBN, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237956 | Indication of Redcap delivery for Broadcast Sessions [Redcap] | Nokia, Nokia Shanghai Bell |
| R3-237959 | Reply LS to SA2 on RedCap UE MBS Broadcast reception | RAN3(ZTE) |
| 8.2 | LSin received during the meeting | |
| R3-237898 | LS on Rel-18 higher-layers parameter list | RAN1(Ericsson) |
| 8.3 | Left over LSs / pending actions | |
| R3-237425 | User Consent Principles | InterDigital, Ericsson |
| R3-237477 | Discussion on user consent for trace reporting | Ericsson, InterDigital |
| R3-237478 | Correction of user consent for MDT | Ericsson, InterDigital |
| R3-237479 | Correction to 38.401 on the user consent for trace reporting | Ericsson, InterDigital |
| R3-237480 | [draft] Reply LS on the user consent for trace reporting | Ericsson |
| R3-237549 | Correction of user consent for MDT | Nokia, Nokia Shanghai Bell |
| R3-237604 | Discuss user consent for trace reporting | ZTE |
| R3-237605 | Correction of user consent for MDT | ZTE |
| R3-237681 | Discussion on user consent for trace reporting | CMCC |
| R3-237724 | Further discussions on the user consent for trace reporting | Huawei |
| R3-237725 | Correction to 38.401 on the user consent for trace reporting | Huawei, CMCC |
| R3-237726 | [draft] Reply LS to R3-234493 (S3-234267) on the user consent for trace reporting | Huawei |
| R3-237727 | Correction to 37.320 on the user consent for trace reporting | Huawei, CMCC |
| R3-237731 | Response to R3-237425 | Huawei Device Co., Ltd |
| R3-237746 | CB:5_UserConsent | Huawei |
| R3-237947 | Correction to 38.401 on the user consent for trace reporting | Huawei, CMCC, Ericsson |
| R3-237948 | Correction to 37.320 on the user consent for trace reporting | Huawei, CMCC |
| R3-237953 | [draft] Reply LS on the user consent for trace reporting | Ericsson |
| R3-237960 | Correction to 38.401 on the user consent for trace reporting | Huawei, CMCC, Ericsson, Interdigtal, ZTE |
| R3-237963 | Correction to 37.320 on the user consent for trace reporting | Huawei, CMCC, Ericsson, Interdigtal, ZTE, Nokia |
| R3-237964 | Reply LS on the user consent for trace reporting | RAN3(Ericsson) |
| 9.1 | LTE | |
| R3-237446 | Restrict handover to NR NTN | Vodafone GmbH |
| R3-237682 | Discussion on QoE Area Scope IE | ZTE, China Telecom, China Unicom |
| R3-237683 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237684 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237685 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237686 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237687 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237688 | Correction on the QoE Area Scope IE in UE Application layer measurement configuration | ZTE, China Telecom, China Unicom |
| R3-237747 | CB:#6_QoEAreaScope | ZTE |
| 9.2 | NR | |
| R3-237193 | Correction of NR E-CID for OnDemand measurements | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, ZTE |
| R3-237194 | Correction of NR E-CID for OnDemand measurements | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, ZTE |
| R3-237197 | Correction on TRP Information Type Response Item IE of Positioning | CATT, Huawei, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237198 | Correction on NR-Mode-Info IE of SON | CATT, ZTE, Huawei, Ericsson, Sumsang, Nokia, Nokia Shanghai Bell |
| R3-237204 | Transferring of IAB authorization status via HO request message | ZTE, Lenovo, CATT, Nokia, Nokia Shanghai Bell |
| R3-237205 | Clarification on gNB-DU Cell Resource Configuration for IAB | ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-237217 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT |
| R3-237218 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT |
| R3-237219 | Correction on small data transmission | Huawei, Qualcomm Incorporated, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, CATT, Lenovo |
| R3-237250 | Correction on Resource Status Request | Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-237251 | Correction on Resource Status Request | Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-237269 | Correction of F1-U Context Reference for PTM | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei |
| R3-237270 | Correction of F1-U Context Reference for PTM | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei |
| R3-237271 | Correction of Interaction with PDU Session Resource Indication | Nokia, Nokia Shanghai Bell |
| R3-237305 | Correction on support of BDS B1C SSR broadcasting | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum R3 |
| R3-237306 | Inactive Time Signaling over F1 for Mobility | Nokia, Nokia Shanghai Bell |
| R3-237312 | Clarification of the RAN UE ID usage in stage-2 | Ericsson, Orange, Deutsche Telekom, AT&T |
| R3-237341 | Correction to NRPPa for the misalignment on DL PRS | ZTE, Samsung, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237342 | Correction to NRPPa for the misalignment on DL PRS | ZTE, Samsung, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237343 | Correction to F1AP for the misalignment on DL PRS | ZTE, Samsung, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237349 | Correction on SHR for intra-NR mobility | Samsung, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-237354 | Correction to F1AP for the misalignment on DL PRS | Samsung, ZTE, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237361 | Correction on IP address allocation for IAB via OAM | Huawei, Lenovo, Samsung, Xiaomi, Ericsson |
| R3-237362 | Correction on IP address allocation for IAB via OAM | Huawei, Lenovo, Samsung, Xiaomi, Ericsson |
| R3-237363 | Correction on IAB authorization status transfer | Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237444 | Restrict handover to eUTRA NTN | Vodafone GmbH |
| R3-237453 | Correction of Data Forwarding Handling of MRB | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Qualcomm Incorporated, Orange, CMCC |
| R3-237461 | Correction of Data Forwarding Handling of MRB | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Qualcomm Incorporated, Orange, CMCC |
| R3-237499 | Solving Misalignment in UE Context Release procedure | Ericsson, China Telecom, ZTE, Verizon Wireless |
| R3-237500 | Solving Misalignment in UE Context Release procedure | Ericsson, China Telecom, ZTE, Verizon Wireless |
| R3-237503 | Correction of NGAP and XnAP QoE Measurement Status IE | Ericsson, Lenovo, CATT, Xiaomi, Samsung |
| R3-237504 | Correction of QoE Measurement Status IE | Ericsson, Lenovo, CATT, Xiaomi, Samsung |
| R3-237505 | Correction of QoE Measurement Status IE | Ericsson, Lenovo, CATT, Xiaomi, Samsung |
| R3-237506 | Correction for I-RNTI | Ericsson, Huawei, China Telecom |
| R3-237507 | XnAP correction for I-RNTI | Ericsson, Huawei, China Telecom |
| R3-237520 | Restrict handover to eUTRA NTN | Vodafone GmbH |
| R3-237521 | XnAP correction for I-RNTI | Ericsson, Huawei, China Telecom |
| R3-237525 | Correction on LCS reporting for UL-AoA | Ericsson |
| R3-237526 | Correction on LCS reporting for UL-AoA | Ericsson |
| R3-237527 | Correction on LCS reporting for UL-AoA | Ericsson |
| R3-237528 | Correction on LCS reporting for UL-AoA | Ericsson |
| R3-237547 | Discussion on providing the PDCP version from the eNB-CP to the eNB-UP over the E1 interface | Samsung |
| R3-237548 | PDCP version information over the E1 interface | Samsung |
| R3-237560 | Data forwarding handling of MRB without source progress | CATT, Nokia, Nokia Shanghai Bell, Orange, CMCC, Qualcomm Incorporated, ZTE |
| R3-237561 | Correction to F1AP on Data forwarding handling of MRB | CATT,Nokia,Nokia Shanghai Bell,Orange,CMCC,Qualcomm Incorporated,Ericsson, ZTE |
| R3-237562 | Discussion on support of multiple F1-U tunnels per MRB | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, CMCC, Samsung, Lenovo,Huawei |
| R3-237563 | Correction on multiple F1-U tunnels for MRB | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, CMCC, CBN, Samsung, Lenovo, Huawei |
| R3-237564 | Correction on multiple F1-U tunnels for MRB | CATT, Nokia, Nokia Shanghai Bell,ZTE,Qualcomm,CMCC, Lenovo,Huawei |
| R3-237565 | ASN.1 and tabular alignment for Multicast related message | CATT |
| R3-237584 | Correction of CPAC to clarify optional late data forwarding | ZTE, LG Electronics, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, NEC, Lenovo, Samsung |
| R3-237613 | Transfer IAB authorization status to F1-terminating IAB-donor | CATT |
| R3-237614 | IAB-node authorization | CATT |
| R3-237652 | Correction on value range of the Extended Packet Delay Budget | Huawei |
| R3-237653 | Correction on value range of the Extended Packet Delay Budget | Huawei |
| R3-237654 | Correction on value range of the Extended Packet Delay Budget | Huawei |
| R3-237699 | Corrections on MN initiated SN Modification procedure | Ericsson |
| R3-237700 | Corrections on MN initiated SN Modification procedure over Xn | Ericsson |
| R3-237709 | Correction on the usage of SN Reconfiguration Complete | ZTE, NEC, China Telecom |
| R3-237710 | Correction on the usage of SN Reconfiguration Complete(37.340) | ZTE, LG Electronics, Google, NEC, China Telecom |
| R3-237711 | Correction on the usage of SN Reconfiguration Complete(38.423) | ZTE |
| R3-237712 | Correction on the usage of SN Reconfiguration Complete(36.423) | ZTE |
| R3-237728 | Correction on Bearer Context Status Change | Huawei, China Unicom, Vodafone |
| R3-237729 | Correction on TRP Information Type Response Item IE of Positioning | CATT, Huawei, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237730 | Correction on NR-Mode-Info IE of SON | CATT, ZTE, Huawei, Ericsson, Sumsang, Nokia, Nokia Shanghai Bell |
| R3-237735 | Response to R3-237503 | ZTE |
| R3-237748 | Correction to F1AP for the misalignment on DL PRS | ZTE, Samsung, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237749 | Clarification on gNB-DU Cell Resource Configuration for IAB | ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-237750 | CB:#7_IABAuthorization | Huawei |
| R3-237751 | CB:#8_R17MBS | CATT |
| R3-237752 | Correction on NR-Mode-Info IE of SON | CATT, ZTE, Huawei, Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R3-237753 | CB:#9_SNReconfigComplete | ZTE |
| R3-237755 | CB:#10_UecontextRelease | Ericsson |
| R3-237756 | Correction on Resource Status Request | Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-237757 | Correction on Resource Status Request | Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-237758 | Clarification of the RAN UE ID usage in stage-2 | Ericsson, Orange, Deutsche Telekom, AT&T, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237760 | CB:#11_MCGRecovery | Huawei |
| R3-237761 | Correction on Bearer Context Status Change | Huawei, China Unicom, Vodafone |
| R3-237762 | Correction of Interaction with PDU Session Resource Indication | Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-237772 | Correction on SHR for intra-NR mobility | Samsung, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-237779 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-237780 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics |
| R3-237812 | Correction of F1-U Context Reference for PTM | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, Ericsson |
| R3-237853 | Correction on multiple F1-U tunnels for MRB | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, CMCC, CBN, Samsung, Lenovo, Huawei, Ericsson |
| R3-237854 | ASN.1 and tabular alignment for Multicast related message | CATT, Nokia, Nokia Shanghai Bell |
| R3-237886 | Solving Misalignment in UE Context Release procedure | Ericsson, China Telecom, ZTE, Verizon Wireless, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-237887 | Correction on IAB authorization status transfer | Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CATT, Xiaomi |
| R3-237888 | IAB-node authorization | CATT, Huawei |
| R3-237945 | Clarification of the RAN UE ID usage in stage-2 | Ericsson, Orange, Deutsche Telekom, AT&T, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237952 | Solving Misalignment in UE Context Release procedure | Ericsson, China Telecom, ZTE, Verizon Wireless, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-238171 | Solving Misalignment in UE Context Release procedure | Ericsson, China Telecom, ZTE, Verizon Wireless, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-238172 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics |
| 10.1 | General | |
| R3-237005 | (BLCR to 38.401) Addition of SON features enhancement | ZTE |
| R3-237006 | (BLCR to 38.470) Addition of SON features enhancement | CMCC |
| R3-237007 | (BLCR to 36.300) Addition of SON features enhancement | Lenovo |
| R3-237008 | (BLCR to 38.300) Addition of SON features enhancement | CMCC |
| R3-237009 | (BLCR to 38.413) for SON | Ericsson |
| R3-237010 | (BLCR to 38.423) for MDT | Huawei |
| R3-237011 | (BL CR to 38.420) SON Introduction of RACH Indication | Huawei |
| R3-237012 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-237013 | (BL CR to 37.320) Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei |
| R3-237014 | (BLCR to 38.413) for MDT | Ericsson |
| R3-237015 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-237016 | (BLCR to 38.473) Addition of SON features enhancement | Huawei |
| R3-237017 | (BLCR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell |
| R3-237167 | Reply LS on RACH enhancement | RAN2(CMCC) |
| R3-237666 | Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI | CMCC |
| R3-237784 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-238072 | Addition of SON features enhancement | Lenovo, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE |
| R3-238073 | Addition of SON features enhancement | CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238074 | (BLCR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-238075 | Addition of SON features enhancement | CMCC, ZTE, Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R3-238076 | Support for SON over NG | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, CMCC, ZTE, CATT |
| R3-238077 | Introduction of MDT enhancements to support Non-Public Networks | Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238078 | Addition of SON features enhancement | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-238138 | Addition of SON features enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-238139 | Addition of SON features enhancement | CMCC, ZTE, Nokia, Nokia Shanghai Bell |
| R3-238140 | SON Introduction of RACH Indication | Huawei, Nokia, Nokia Shanghai Bell |
| R3-238141 | Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei |
| R3-238142 | Introduction of MDT enhancements to support Non-Public Networks | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-238143 | Addition of SON features enhancement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| 10.2.1 | SHR and SPR | |
| R3-237146 | Reply LS on SHR and SPR | RAN2(Nokia) |
| R3-237252 | (TPs for SON BLCRs for TS 38.300, 38.413, 38.423, 38.473) SHR and SPR | Huawei |
| R3-237350 | (TP for SON BLCR for 38.423 and TS38.300) SON enhancement for SHR | Samsung |
| R3-237351 | (TP for SON BLCR for 37.340 and 38.423) SON enhancement for SPR | Samsung |
| R3-237401 | Discussion on SON enhancements for inter-RAT SHR and SPR | Lenovo |
| R3-237511 | (TP for SON BL CR for TS 37.340, TS 38.423) SPR for SON rel-18 | Ericsson |
| R3-237545 | [TP for SON BLCR for 37.340] Remaining issues on SPR | Nokia, Nokia Shanghai Bell |
| R3-237585 | (TP for SON 37.340, 38.423 and 36.423) Discussion on SON enhancement for SHR and SPR | CATT |
| R3-237606 | (TPs for SON BLCRs for TS 38.413 38.423)Inter-RAT SHR and SPR | ZTE |
| R3-237667 | Discussion on SON enhancement for SPR | CMCC |
| R3-237785 | CB:#SONMDT1_SHRSPR | Samsung |
| R3-237930 | (TP for SON BLCRs for TS 38.413)Inter-RAT SHR and SPR | ZTE |
| R3-237931 | (TP for SON BL CR for TS 38.423) SPR for SON Rel-18 | Ericsson |
| R3-237944 | (TP for SON BLCR for TS38.300) SON enhancement for SHR | Samsung |
| R3-237962 | (TP for SON BL CR for TS 38.423) Inter-RAT SHR for SON Rel-18 | CATT |
| R3-237990 | (TP for SON BLCRs for TS 38.413) Inter-RAT SHR | ZTE, Samsung |
| R3-237992 | (TP for SON BL CR for TS 38.423) Inter-RAT SHR for SON Rel-18 | CATT, Samsung |
| R3-237993 | (TP for SON BLCR for TS38.300) SON enhancement for SHR | Samsung |
| R3-237995 | (TP for SON BL CR for TS 38.423) SPR for SON Rel-18 | Ericsson |
| 10.2.2 | MRO | |
| R3-237245 | Discussion on remaining issue of fast MCG recovery | NEC |
| R3-237253 | (TPs for SON BLCRs for TS 37.340, 38.300,36.300, 38.413, 38.423) MRO | Huawei |
| R3-237336 | (TPs for SON BL CR 37.340 and 38.423) MRO for CPAC | ZTE |
| R3-237352 | (TP for SON BLCR for 38.423 and 37.340) SON enhancements for CPAC | Samsung |
| R3-237353 | (TP for SON BLCR for 38.413) MRO for inter-system handover for voice fallback and the fast MCG recovery | Samsung |
| R3-237402 | (TP to BLCR for TS37.340 and TS38.423) MRO for CPAC | Lenovo |
| R3-237403 | (TP to BLCR for TS38.413) MRO for fast MCG recovery and inter-system handover for voice fallback | Lenovo |
| R3-237512 | (TP for SON BL CR for TS 38.413) SON enhancements for MRO | Ericsson |
| R3-237513 | (TP for SON BL CR for TS 37.340) Clarification on CPAC failure definitions | Ericsson |
| R3-237546 | (TP for SON BLCR for 37.340) SON enhancements for CPAC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-237586 | (TP for SON 37.340 and 38.423) Discussion on MRO enhancement for CPAC | CATT |
| R3-237587 | (TP for SON 38.413) Discussion on MRO enhancement for fast MCG recovery and voice fallback | CATT |
| R3-237668 | Discussion on MRO for CPAC | CMCC |
| R3-237669 | Discussion on MRO for fast MCG recovery | CMCC |
| R3-237703 | (TP for SON BL CR 36.300) Stage 2 clean-up on MRO for inter-system handover for voice fallback | ZTE, China Telecom, China Unicom |
| R3-237704 | (TP for SON BL CR 38.300) Stage 2 clean-up on MRO for inter-system handover for voice fallback | ZTE, China Telecom, China Unicom |
| R3-237705 | (TP for SON BL CR 38.413) MRO for inter-system handover for voice fallback | ZTE, China Telecom, China Unicom |
| R3-237786 | CB:#SONMDT2_MRO | Nokia |
| R3-237896 | (TP for SON BLCR for TS36.300) MRO | Huawei |
| R3-237907 | (TP for SON BL CR for TS 38.413) SON enhancements for Mobility Robustness Optimization | Ericsson |
| R3-237932 | (TP for SON BL CR 38.300) Stage 2 clean-up on MRO for inter-system handover for voice fallback | ZTE, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-237937 | (TP for SON BLCR for 37.340) SON enhancements for CPAC | Samsung, Nokia, Nokia Shanghai Bell |
| 10.2.3 | RACH Enhancements | |
| R3-237314 | (TP for SON BLCR for TS 38.423): Clean-up for RACH Enhancement | Huawei, CMCC, China Unicom |
| R3-237315 | (TP for SON BLCR for TS 36.423): Clean-up for RACH Enhancement | Huawei, CMCC, China Unicom |
| R3-237455 | RA Report enhancements for identifying RACH partitoning configuration | Qualcomm Incorporated |
| R3-237514 | RACH Optimization enhancement | Ericsson |
| 10.2.4 | SON/MDT Enhancements for Non-Public Networks | |
| R3-237143 | Reply LS on potential override of logged MDT reports upon moving from SNPN to PLMN | RAN2(CATT) |
| R3-237156 | Reply LS on user consent of Non-public Network | SA5(Ericsson) |
| R3-237206 | (TP for MDT BLCR for TS 38.423): Clean-up for MDT for NPN | Huawei |
| R3-237450 | (TP for TS 38.413) Updates of MDT area scope for NPN in NGAP and XnAP | Nokia, Nokia Shanghai Bell |
| R3-237515 | (TP for SON BLCR to TS 38.413 and TS 38.423) SON enhancements for Non-public networks | Ericsson |
| R3-237607 | (TPs for MDT BLCRs for TS 38.423)MDT support in NPN | ZTE, CMCC,China Unicom |
| R3-237787 | (TPs for MDT BLCRs for TS 38.423) MDT support in NPN | ZTE, CMCC, China Unicom, Ericsson |
| R3-237788 | CB:#SONMDT3_NPN | ZTE |
| R3-237965 | (TP for MDT BLCR for TS38.413) MDT support in NPN | Huawei |
| 10.2.5 | SON for NR-U | |
| R3-237187 | Conclusion of the discussion on SON for NR-U | Nokia, Nokia Shanghai Bell |
| R3-237207 | (TP for SON BL CR for TS 38.300): SON for NR-U | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| R3-237322 | Discussion on SON for NR-U | Samsung |
| R3-237337 | (TP for SON BL CR 38.300) Stage 2 clean-up on MRO for NR-U | ZTE |
| R3-237404 | Discussion on MRO for NR-U | Lenovo |
| R3-237456 | SON enhancements for NR-U | Qualcomm Incorporated |
| R3-237508 | (TP for SON to BLCR for TS 38.300) LBT failures in MRO | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-237509 | (TP for SON to BLCR for TS 38.473, TS 38.423) NR-U enhancements for MLB and MRO | Ericsson |
| R3-237588 | Discussion on SON enhancement for NR-U | CATT |
| R3-237789 | CB:#SONMDT4_NR-U | Ericsson |
| R3-237802 | (TP for SON to BLCR for TS 38.300) LBT failures in MRO | Ericsson, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-237803 | Ericsson, Samsung, Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm Incorporated | Ericsson |
| R3-238002 | (TP for SON to BLCR for TS 38.423) LBT failures in MRO | Ericsson, Samsung, Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm Incorporated |
| 11.1 | General | |
| R3-237018 | (BLCR to 38.470) Introduction of R18 QoE measurement | Lenovo, ZTE, Ericsson, Huawei, Samsung, Nokia, Nokia Shanghai Bell |
| R3-237019 | (BL CR to 37.340) QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson |
| R3-237020 | (BLCR to 38.300) Introduction of R18 QoE measurement Title | China Unicom |
| R3-237021 | (BL CR to 38.401) Introduction of R18 QoE measurement | Samsung |
| R3-237022 | (BLCR to 38.413) Introduction of R18 QoE measurement | Huawei, China Telecom, China Unicom |
| R3-237023 | (BLCR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| R3-237024 | (BLCR to 38.473) Introduction of R18 QoE measurement | ZTE |
| R3-237706 | Update Workplan for Rel-18 NR QoE Enhancement | China Unicom |
| R3-237707 | (BLCR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-237903 | (BLCR to 38.413) Introduction of R18 QoE measurement | Huawei, China Telecom, China Unicom |
| R3-237904 | (BLCR to 38.470) Introduction of R18 QoE measurement | Lenovo, ZTE, Ericsson, Huawei, Samsung, Nokia |
| R3-237905 | (BLCR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| R3-237906 | (BLCR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-238102 | QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson, Xiaomi, CATT, NEC, Lenovo |
| R3-238103 | Introduction of R18 QoE measurement enhancements | China Unicom, Ericsson,CATT, Xiaomi, ZTE, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-238105 | Introduction of R18 QoE measurement enhancements | Huawei, China Telecom, China Unicom, Ericsson, CATT, NEC, Nokia, Nokia Shanghai Bell |
| R3-238106 | Introduction of R18 QoE measurement enhancements | Ericsson, CATT, NEC, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-238107 | Introduction of R18 QoE measurement enhancements | ZTE, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell, CATT, Ericsson, NEC |
| R3-238144 | Introduction of R18 QoE measurement enhancements | Samsung, Ericsson, NEC, Nokia, Nokia Shanghai Bell |
| R3-238145 | Introduction of R18 QoE measurement enhancements | Lenovo, ZTE, Ericsson, Huawei, Samsung, Nokia, Nokia Shanghai Bell, NEC |
| 11.2 | Support for New Service Type and RRC_INACTIVE/RRC_IDLE states | |
| R3-237142 | Reply LS on area scope for QoE measurements | RAN2(Qualcomm) |
| R3-237179 | (TP for QoE BL CR for TS 38.413) QoE and RVQoE Measurement Support for MBS | Ericsson |
| R3-237242 | Discussion on INACTIVE&IDLE QoE | NEC |
| R3-237383 | (TP for TS 38.300) QMC support for RRC_IDLE | Xiaomi |
| R3-237405 | (TPs for BLCR 38.423 and 38.420) Remaining issues on QoE measurement in RRC_INACTIVE and RRC_IDLE states | Lenovo |
| R3-237447 | (TP for TS 38.413) Storage/retrieval of QMC context | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, Orange |
| R3-237448 | (TP for TS 38.413) Handling of failed MBS QMC activation | Nokia, Nokia Shanghai Bell |
| R3-237457 | QMC for applications carried over MBS broadcast and multicast | Qualcomm Incorporated |
| R3-237458 | QoE enhancements for UEs in HSDN cells and high speed | Qualcomm Incorporated |
| R3-237593 | TP to BLCR for 38.413 on NR QoE in RRC_INACTIVE/RRC_IDLE states | CATT |
| R3-237594 | [Draft] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE | CATT |
| R3-237637 | Leftover issues on QMC for MBS and RRC state | Samsung |
| R3-237689 | Discussion on IDLE INACTIVE QoE with draft LS | ZTE, China Telecom, CMCC |
| R3-237690 | TP to 38423 and 38300 for INACTIVE IDLE QoE | ZTE, China Telecom, China Unicom |
| R3-237708 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | China Unicom |
| R3-237718 | Further discussions on QoE measurement for MBS service | Huawei |
| R3-237719 | (TP to BL CR of 38.413) on support of QoE measurement continuity in unicast for MBS service | Huawei, China Telecom, China Unicom |
| R3-237738 | LS reply for LS on QMC support in RRC_IDLE and RRC_INACTIVE | SA3(Nokia) |
| R3-237871 | Summary of offline discussion on CB on QoE RRC_IDLE/INACTIVE | Lenovo |
| R3-237910 | CB:#QoE1_Inactive | Lenovo |
| R3-237971 | (TP to BL CR of 38.413) on support of QoE measurement for MBS service | Huawei, China Telecom, China Unicom |
| R3-237972 | (TP to BL CR of 38.300) on support of QoE measurement for MBS service | Huawei |
| R3-237983 | [Draft] Support for MCE ID | Ericsson |
| R3-237996 | TP to 38423 BLCR for INACTIVE/IDLE QoE | ZTE, China Telecom, CMCC |
| R3-237997 | LS on QMC support in RRC_IDLE and RRC_INACTIVE | RAN3(ZTE) |
| R3-238003 | Support for MCE ID | RAN3(Ericsson) |
| R3-238004 | TP to 38423 BLCR for INACTIVE/IDLE QoE | ZTE, China Telecom, CMCC |
| 11.3 | Support QoE for NR-DC | |
| R3-237180 | (TP for QoE BL CR for TS 38.423, TS 37.340, and TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | Ericsson |
| R3-237406 | On remaining issues of QoE measurement in NR-DC | Lenovo |
| R3-237449 | Discussion on QoE/RVQoE measurement report continuity during SCG/MCG failure | Nokia, Nokia Shanghai Bell |
| R3-237459 | Support for QoE in NR-DC | Qualcomm Incorporated |
| R3-237510 | (draft CR to 38.420) QMC enhancements for NR-DC | Qualcomm Technologies Int |
| R3-237595 | Discussion on Support for QoE in NR-DC | CATT |
| R3-237638 | Leftovers for QMC support of NR-DC | Samsung |
| R3-237651 | Discussion on RAN overload in NR-DC | Nokia, Nokia Shanghai Bell |
| R3-237655 | Discussion on the remaining issues on QoE enhancement for NR-DC | ZTE, China Telecom |
| R3-237656 | Stage 2 TPs to BL CR of 37.340 and 38.300 on QoE in NR-DC | ZTE, China Telecom |
| R3-237657 | (TP to BLCR of 38.423) QoE enhancement for NR-DC | ZTE, China Telecom |
| R3-237716 | (TP to BL CR of 38.300 38.423 37.340) QoE in NR-DC | China Unicom |
| R3-237720 | Further discussions on QoE measurement for NR-DC | Huawei |
| R3-237721 | (TP to BL CR of 38.423) on QoE measurement enhancements in DC | Huawei, China Telecom, China Unicom |
| R3-237897 | Summary of offline discussion on QoE in NR-DC | ZTE |
| R3-237899 | (TP for QoE BL CR for TS 38.423): QoE support in NR-DC | Ericsson |
| R3-237911 | CB:#QoE2_NRDC | ZTE |
| R3-237933 | (TP for BL CR for TS 37.340) on QoE in NR-DC | ZTE, China Telecom |
| R3-237934 | (draft CR to 38.420) QMC enhancements for NR-DC | Qualcomm Technologies Int |
| R3-237935 | (TP for BLCR for TS 38.300) on QoE in NR-DC | Huawei |
| R3-238039 | (TP for QoE BL CR for TS 38.423): QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | Ericsson |
| R3-238040 | (TP to BL CR of 38.300) on QoE measurement enhancements in DC | Huawei |
| R3-238041 | (TP to BL CR of 37.340) on QoE enhancement in NR-DC | ZTE, China Telecom, Ericsson |
| R3-238042 | (BL CR to 38.420) QMC enhancements for NR-DC | Qualcomm Technologies Int |
| R3-238146 | QMC enhancements for NR-DC | Qualcomm Technologies Int, Nokia, Nokia Shanghai Bell |
| 11.4 | Others | |
| R3-237181 | (TPs for QoE BL CRs for TS 38.413 and TS 38.423) Enhancements of Rel-17 QoE and RVQoE Features | Ericsson |
| R3-237243 | Discussion on intra-5GC Inter-RAT handover | NEC |
| R3-237658 | Further discussion on other issues | ZTE, China Telecom, China Unicom, CMCC |
| R3-237659 | (TPs for BL CR of TS38.401&38.473) Deactivation of RVQoE reporting over F1AP | ZTE, China Telecom, China Unicom |
| R3-237717 | (TP to BL CR of 38.413) Inter-RAT mobility for QoE measurement | China Unicom |
| R3-237722 | Further discussion on remaining open issues and leftovers | Huawei |
| R3-237723 | (TP to BL CR of 38.300) on intra-system inter-RAT handover and CHO for QoE measurement | Huawei, China Telecom, China Unicom |
| R3-237889 | summary of offline discussion on QoE others | Huawei |
| R3-237912 | CB:#QoE3_Others | Huawei |
| R3-237957 | (TP to BLCR of 38.473) Deactivation of RVQoE reporting over F1AP | ZTE, China Telecom, China Unicom |
| R3-237970 | (TP to BL CR of 38.300) on intra-system inter-RAT handover and CHO for QoE measurement | Huawei, China Telecom, China Unicom |
| R3-237976 | TP for 38.410 on Introduction of R18 QoE measurement | CATT |
| R3-238006 | (TP to BL CR of 38.300) on intra-system inter-RAT handover and CHO for QoE measurement | Huawei, China Telecom, China Unicom |
| R3-238007 | (TP to BLCR of 38.473) Deactivation of RVQoE reporting over F1AP | ZTE, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-238104 | Introduction of R18 QoE measurement enhancements | CATT, NEC, Ericsson, Nokia, Nokia Shanghai Bell |
| 12.1 | General | |
| R3-237025 | (BL CR to TS 38.401) for addition of AI/ML-RAN feature in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC |
| R3-237026 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated |
| R3-237027 | (BL CR to 38.420) Support of AIML for NG-RAN | CATT, Nokia, Nokia Shanghai Bell |
| R3-237028 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson |
| R3-237790 | (BL CR to TS 38.401) for addition of AI/ML-RAN feature in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC |
| R3-237791 | (BL CR to 38.420) Support of AIML for NG-RAN | CATT, Nokia, Nokia Shanghai Bell |
| R3-237792 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-238069 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated, China Telecom, NEC, LGE |
| R3-238070 | (CR to 38.420) Support of AIML for NG-RAN | CATT, Nokia, Nokia Shanghai Bell, NEC, Huawei, Lenovo, ZTE, Ericsson |
| R3-238071 | Support of AI/ML in NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, NEC, Qualcomm Incorporated, Huawei |
| R3-238147 | Support of AI/ML in NG-RAN in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC, NEC |
| 12.2.1 | Stage2 Related | |
| R3-237290 | (TP to 38.300 BLCR) Stage2 description update for AIML RAN | ZTE, Samsung, CMCC, China Telecom, China Unicom |
| R3-237291 | (TP for BLCR 38.401) Stage2 impact of E1&F1 interface for AIRAN | ZTE, Samsung, CMCC, China Telecom, China Unicom |
| R3-237378 | (TP for AI/ML BLCR for TS 38.300) Further discussions on common issues and Stage 2 updates on the introduction of RAN AI/ML | Huawei |
| R3-237407 | (TPs for BLCR to TS 38.300 and TS 38.420) Corrections on terminology | Lenovo |
| R3-237487 | Discussions on stage 2 issues | Ericsson, AT&T, InterDigital |
| R3-237488 | (TP for AI/ML BLCR to TS38.300) Characteristics of the procedures for exchanging AI/ML-related information | Ericsson, AT&T, InterDigital |
| R3-237576 | (TP to TS 38.300) Stage 2 Updates | Nokia, Nokia Shanghai Bell |
| R3-237793 | (TP to 38.300 BLCR) Stage2 description update for AIML RAN | ZTE, Samsung, CMCC, China Telecom, China Unicom |
| R3-237794 | (TPs for BLCR to TS 38.420) Corrections on terminology | Lenovo, ZTE, Samsung, CMCC, China Telecom, China Unicom, Huawei, Nokia, Nokia Shanghai Bell, NEC, Qualcomm Incorporated, Ericsson, CATT, LGE |
| R3-238008 | (TP to 38.300 BLCR) Stage2 description update for AI/ML RAN | ZTE, Samsung, CMCC, China Telecom, China Unicom, Huawei, Lenovo, Nokia, Nokia Shanghai Bell, NEC, Qualcomm Incorporated, Ericsson, CATT ,LGE, InterDigital |
| 12.2.2.1 | LB and Xn procedures | |
| R3-237172 | Discussion on UE performance feedback | CATT |
| R3-237173 | TP to BLCR for 38.423 on AL/ML load balance and FFS clear up | CATT |
| R3-237238 | RAN AI/ML on UE Performance Feedback | NEC |
| R3-237239 | (TP to TS 38.423 on RAN AI/ML) on UE Performance Feedback | NEC |
| R3-237256 | Discussion on remaining open issues in UE performance for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-237292 | Futher discussion on remaining issues for Load Balancing | ZTE |
| R3-237293 | (TP to 38.423 BLCR) AIML based Load Balancing | ZTE |
| R3-237323 | (TP to TS 38.423 BLCR) Failed Report Characteristics of UE Performance Feedback and Measured UE Trajectory | Samsung |
| R3-237324 | (TP to TS 38.423 BLCR) Support of AI/ML for LB | Samsung |
| R3-237379 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Load Balancing use case | Huawei |
| R3-237408 | Left issues related to load balancing use case | Lenovo |
| R3-237409 | (TP for TS38.423 BLCR) On UE related feedback collection | Lenovo |
| R3-237423 | Discussion on the open issue for AI/ML load balancing | LG Electronics Inc. |
| R3-237424 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on the open issue for AI/ML load balancing | LG Electronics Inc. |
| R3-237481 | Periodic UE Performance Feedback measurements collection and reporting | Ericsson, Deutsche Telekom, InterDigital |
| R3-237482 | (TP for AIML BL CR for TS 38.423) Periodic UE Performance Feedback measurements collection and reporting | Ericsson, Deutsche Telekom, InterDigital |
| R3-237483 | Cause values for Data Collection Reporting Initiation | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237484 | (TP for AIML for BLCR to TS38.423) Cause values for Data Collection Reporting Initiation | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237485 | Data Collection Reporting clean-up | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237486 | (TP for AIML for BLCR to TS38423) Data Collection Reporting clean-up | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237577 | (TP to BL CR for TS 38.423) Cause Value Discussion and Other Open Issues | Nokia, Nokia Shanghai Bell |
| R3-237578 | (TP to BL CR for TS 38.423) UE Performance Data Collection | Nokia, Nokia Shanghai Bell |
| R3-237579 | Discussion on Predicted Radio Resource Status | Nokia, Nokia Shanghai Bell, BT, Orange |
| R3-237580 | (TP to BL CR for TS 38.423) Predicted Radio Resource Status | Nokia, Nokia Shanghai Bell, BT, Orange |
| R3-237673 | Discussion on AIML remaining issues | CMCC |
| R3-237674 | (TP for 38.423)Procedure for Load Balancing | CMCC |
| R3-237796 | CB:#AIML2_LB | ZTE |
| R3-237939 | (TP for BL CR for TS 38.423) AIML based Load Balancing | ZTE |
| R3-237940 | (TP to BL CR for TS 38.423) UE Performance Data Collection | Nokia, Nokia Shanghai Bell |
| R3-237941 | (TP for BL CR for TS 38.423) Failed Report Characteristics of UE Performance Feedback and Measured UE Trajectory | Samsung |
| R3-237977 | (TP for BL CR for TS 38.423) Failed Report Characteristics of UE Performance Feedback and Measured UE Trajectory | Samsung |
| R3-238009 | (TP for BL CR for TS 38.423) AIML based Load Balancing | ZTE, Huawei, Ericsson, NEC, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CATT, Deutsche Telekom, Samsung, Lenovo, InterDigital |
| R3-238010 | (TP to BL CR for TS 38.423) UE Performance Data Collection | Nokia, Nokia Shanghai Bell |
| R3-238011 | (TP for BL CR for TS 38.423) Failed Report Characteristics of UE Performance Feedback and Measured UE Trajectory | Samsung, Cybercore, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, Lenovo |
| R3-238061 | (TP to BL CR for TS 38.423) UE Performance Data Collection | Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson, NEC, Huawei,CATT, Lenovo |
| 12.2.2.2 | ME and Xn procedures | |
| R3-237174 | Support of AI/ML based mobility optimization | CATT |
| R3-237175 | TP to BLCR for TS 38.423 on AI/ML based mobility optimization | CATT |
| R3-237240 | AI/ML Configuration of Measured UE Trajectory information | NEC |
| R3-237241 | (TP to TS 38.423 on RAN AI/ML) Configuration of Measured UE Trajectory information | NEC |
| R3-237257 | Discussion on open issues in UE Trajectory Prediction and Feedback | Qualcomm Incorporated |
| R3-237294 | Futher discussion on remaining issues for Mobility Optimization | ZTE |
| R3-237295 | (TP to 38.423 BLCR) AIML based Mobility Optimization | ZTE |
| R3-237325 | (TP to TS 38.423 BLCR) Support of AI/ML for ME | Samsung |
| R3-237380 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Mobility Enhancements use case | Huawei |
| R3-237410 | Left issues related to mobility enhancement use case | Lenovo |
| R3-237493 | Cell based UE trajectory prediction configuration | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237494 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, Deutsche Telekom, AT&T, InterDigital |
| R3-237568 | Discussion on remaining issues for UE trajectory | China Telecommunication |
| R3-237569 | (TP for BLCR of TS 38.423) On support of measured UE trajectory | China Telecommunication |
| R3-237581 | (TP to BL CR for TS 38.423) Measured UE Trajectory | Nokia, Nokia Shanghai Bell |
| R3-237670 | Discussion on Measured UE Trajectory Collection | CMCC |
| R3-237798 | CB:#AIML3_ME | CATT |
| R3-237967 | TP to BLCR for TS 38.423 on AI/ML based mobility optimization | CATT, Huawei, CMCC, LGE, ZTE, Ericsson, NEC, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Deutsche Telekom, Samsung, Lenovo, InterDigital |
| 12.2.2.3 | ES and Xn procedures | |
| R3-237296 | (TP to 38.423 BLCR)Further discussion on remaining issues for Energy Saving | ZTE, Lenovo, China Telecom, China Unicom |
| R3-237326 | (TP to TS 38.423 BLCR) Support of AI/ML for ES | Samsung |
| R3-237381 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Energy Saving use case | Huawei |
| R3-237491 | AI/ML Network Energy Saving | Ericsson, Deutsche Telekom, AT&T, Orange |
| R3-237492 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | Ericsson, Deutsche Telekom, AT&T, Orange |
| R3-237582 | Energy Cost Reporting | Nokia, Nokia Shanghai Bell, Deutsche Telekom, BT, Orange |
| R3-237583 | (TP to BL CR for TS 38.423) AI/ML Energy Saving | Nokia, Nokia Shanghai Bell, Deutsche Telekom, BT, Orange |
| 13.1 | General | |
| R3-237029 | (BL CR to 38.305) Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237030 | (BLCR to 38.413) Support for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-237031 | (BL CR to 38.401) Support for mobile IAB | Huawei |
| R3-237032 | (BL CR to 38.423) Support for mobile IAB | Samsung |
| R3-237033 | (BL CR to 38.455) Support for mobile TRP Location Information | Xiaomi, Ericsson, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-237034 | (BL CR to 38.473): Support for mobile IAB | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-237035 | (BL CR to 38.470) Support of mobile IAB | ZTE |
| R3-237277 | Updated workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R3-237801 | Offline discussion for mobile IAB | Qualcomm |
| R3-237833 | (BL CR to 38.305) Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237834 | (BL CR to 38.423) Support for mobile IAB | Samsung |
| R3-237835 | (BL CR to 38.470) Support of mobile IAB | ZTE |
| R3-237885 | (BL CR to 38.305) Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238093 | Support for mobile IAB | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-238094 | (CR to 38.413) Support for mobile IAB | Nokia, Nokia Shanghai Bell, Ericsson, Xiaomi |
| R3-238095 | Support for mobile IAB | Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-238096 | (CR to 38.473): Support for mobile IAB | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Samsung |
| R3-238148 | (CR to 38.455) Support for mobile TRP Location Information | Xiaomi, Ericsson, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-238149 | (CR to 38.470) Support of mobile IAB | ZTE |
| R3-238150 | (CR to 38.305) Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| 13.2 | Support IAB-node mobility | |
| R3-237183 | Discussion on IAB-node mobility | CANON Research Centre France |
| R3-237188 | (TP for mIAB BL CR for TS 38.423 and TS 38.401): Remaining Issues Related to Mobile IAB-Node Authorization and Migration | Ericsson |
| R3-237199 | (TP for Mobile IAB BL CR) Inter-donor migration in mobile IAB scenario | ZTE |
| R3-237200 | (TP for Mobile IAB BL CR for TS 38.413) Transfer of mobile IAB authorization state in NGAP DOWNLINK NAS TRANSPORT | ZTE, Lenovo, Samsung, CATT, Nokia, Nokia Shanghai Bell, Fujitsu |
| R3-237211 | Remaining issues on supporting IAB-node mobility | Fujitsu |
| R3-237278 | (TP to TS 38.401) BL ST2 procedures for mobile IAB | Qualcomm Inc. |
| R3-237279 | Open issues for mobile IAB topology adaptation and authorization | Qualcomm Inc. |
| R3-237355 | (TP for NR_mobile_IAB BL CRs for TS 38.401/ 38.423) Support of mobility for mobile IAB | Huawei |
| R3-237384 | (TPs to TS 38.423 and TS 38.401) Support of mobile IAB authorization | Xiaomi |
| R3-237385 | (TPs for TS 38.401, TS 38.423, TS 38.473) Support of mobile IAB-DU Migration | Xiaomi |
| R3-237411 | (TP to TS 38.420 BL CR) Discussion on mobile IAB-MT handover | Lenovo |
| R3-237412 | (TP to TS 38.473 BL CR) Discussion on mIAB-DU migration | Lenovo |
| R3-237430 | (TP for Mobile IAB TS38.413 BL CR) Discussion on Support IAB-node mobility with no PDU session | Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-237431 | (TP for Mobile IAB TS38.423 BL CR) Add Mobile IAB Authorized Status IE in the XnAP Retrieve UE Context procedure | Nokia, Nokia Shanghai Bell |
| R3-237469 | Discussion on concurrent MT and DU migrations of mIAB | MITRE Corporation |
| R3-237601 | Discussion on IAB-node mobility | Samsung |
| R3-237612 | (TP to NR_mobile_IAB BL CR of TS 38.473) Co-location discovery for mIAB-MT and mIAB-DU and mIAB-DU migration triggered by OAM | Huawei |
| R3-237615 | (TP to mobile IAB BL CR for TS 38.401) Discussion on support of IAB-node mobility | CATT |
| R3-237616 | (TP to mobile IAB BL CR for TS 38.423) Consideration on IAB-node authorization | CATT |
| R3-237836 | (BL CR to 38.420) Support of mobile IAB | Lenovo |
| R3-237837 | TP for BLCR to TS38.401 | Huawei |
| R3-237838 | TP for BLCR to TS38.473 | ZTE |
| R3-237839 | (TP for NR_mobile_IAB BL CR to TS 38.423) Support IAB-node mobility | Samsung |
| R3-237857 | CB:SoD | Qualcomm |
| R3-237975 | (TP for Mobile IAB TS38.423 BL CR) Add Mobile IAB Authorized Status IE in the XnAP Retrieve UE Context procedure | Nokia, Nokia Shanghai Bell |
| R3-237979 | (TP for mIAB BL CR to TS 38.413) Introduction of mobile IAB supported indication in NG SETUP RESPONSE message | ZTE, Nokia, Nokia Shanghai Bell |
| R3-237987 | (TP to NR_mobile_IAB BL CR of TS 38.473) Mobile IAB-DU migration triggered by OAM | Huawei |
| R3-238016 | (TP for Mobile IAB TS38.423 BL CR) Add Mobile IAB Authorized Status IE in the XnAP Retrieve UE Context procedure | Nokia, Nokia Shanghai Bell |
| R3-238017 | TP for BLCR to TS38.473 | ZTE |
| R3-238021 | (TP for mIAB BL CR for TS 38.413): IAB-node De-registration Handling | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238030 | SoD CB: # IAB-node_mobility | Qualcomm |
| R3-238031 | (TP for NR_mobile_IAB BL CR for TS 38.401) Change for CB: # IAB-node_mobility | Huawei |
| R3-238035 | SoD CB: # IAB-node_mobility | Qualcomm |
| R3-238044 | (TP for NR_mobile_IAB BL CR for TS 38.401) Support of mobility for mobile IAB | Huawei, Xiaomi, Nokia, Nokia Shanghai Bell |
| R3-238045 | (TP for mIAB BL CR to TS 38.473) Usage of BAP address in F1 SETUP REQUEST message | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-238046 | (TP for Mobile IAB TS38.423 BL CR) Add Mobile IAB Authorized Status IE in the XnAP Retrieve UE Context procedure | Nokia, Nokia Shanghai Bell |
| R3-238151 | Support of mobile IAB | Lenovo, Ericsson, Nokia, Nokia Shanghai Bell |
| 13.3 | Mobility Enhancements | |
| R3-237189 | TAC and RANAC Update for mIAB-nodes | Ericsson |
| R3-237201 | (TP for Mobile IAB BL CR for TS 38.473) Enhancements to IAB node migration in mobile IAB scenario | ZTE |
| R3-237280 | Configuration of NCGI and TAC for mIAB | Qualcomm Inc. |
| R3-237356 | (TP for NR_mobile_IAB BL CR for TS 38.401/38.473): Mobility enhancement for mobile IAB | Huawei |
| R3-237413 | Mobility enhancements for mobile IAB-node and its served UE | Lenovo |
| R3-237432 | (TP for TS38.423 BL CR) Discussion on IAB configuration and Mobility Enhancements | Nokia, Nokia Shanghai Bell |
| R3-237602 | Discussion on mobility enhancements | Samsung |
| R3-237617 | (TPs to mobile IAB BL CR for TS 38.401/38.473) Enhancements for mobile IAB | CATT |
| R3-237908 | (TP for NR_mobile_IAB BL CR for TS 38.401) TAC/RANAC configuration for mobile IAB | Huawei |
| R3-237914 | LS on RAN3 agreements on mobile IAB | ZTE |
| R3-237982 | (TP for TS38.423 BL CR) Mobile IAB cell indication | Nokia, Nokia Shanghai Bell |
| R3-238015 | (TP for TS38.423 BL CR) Mobile IAB cell indication | Nokia, Nokia Shanghai Bell |
| R3-238029 | LS on RAN3 agreements on mobile IAB | ZTE |
| R3-238043 | LS on RAN3 agreements on mobile IAB | RAN3(ZTE) |
| 13.4 | Mitigation of interference | |
| R3-237184 | PCI Collision Avoidance with Mobile IAB | CANON Research Centre France |
| R3-237190 | PCI Collision Mitigation for Mobile IAB-Nodes | Ericsson |
| R3-237202 | Discussion on PCI collision avoidance for mobile IAB | ZTE |
| R3-237414 | PCI collision mitigation of mobile IAB-node mobility | Lenovo |
| R3-237433 | Mobile IAB interference mitigation | Nokia, Nokia Shanghai Bell |
| R3-237603 | Discussion on mitigation of interference | Samsung |
| 13.5 | Others | |
| R3-237191 | Remaining Issues Related to Mobile IAB-node-based Positioning | Ericsson |
| R3-237203 | Discussion on LS on UE RACH-less handover for mIAB | ZTE |
| R3-237281 | Discussion on reply LS to RAN2 on RACHless HO for mIAB | Qualcomm Inc. |
| R3-237357 | (TP for NR_mobile_IAB BL CR for TS 38.473): Support of RACH-less HO for mobile IAB | Huawei |
| R3-237358 | [draft] Reply LS to R3-235036/R2-2306817 on UE RACH-less handover for mobile IAB | Huawei |
| R3-237386 | (Reply LS to RAN2) RACH-less HO in mobile DU migration | Xiaomi |
| R3-237856 | [Draft] Reply LS on UE RACH-less handover for mobile IAB | Qualcomm |
| R3-238048 | Reply LS on UE RACH-less handover for mobile IAB | RAN3(Qualcomm) |
| 14.1 | General | |
| R3-237036 | (BLCR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-237037 | (BLCR to 38.401) for L1L2Mob | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237038 | (BL CR to 38.423) Introduction of CHO with SCG(s) | Lenovo, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237039 | (BL CR to TS 38.423) Introduction of Subsequent CPAC | Huawei, ZTE |
| R3-237040 | (BLCR to 38.473) Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE |
| R3-237041 | (BL CR to 38.473) On Subsequent CPAC | Lenovo |
| R3-237042 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| R3-237813 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| R3-238001 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson, Qualcomm Incorporated |
| R3-238085 | Introduction of CHO with SCG(s) | CATT, LG Electronics, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson |
| R3-238086 | Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson, Qualcomm Incorporated, NEC, Nokia, Nokia Shanghai Bell, Lenovo, CATT |
| R3-238088 | Introduction of L1L2Mob and S-CPAC | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, NEC, LG Electronics, Lenovo, Samsung, CATT, Google |
| R3-238089 | Introduction of CHO with SCG(s) | Lenovo, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, CATT, ZTE, Samsung |
| R3-238090 | Introduction of Subsequent CPAC | Huawei, ZTE, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, Lenovo, CATT |
| R3-238152 | Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC, LG Electronics Inc., Lenovo, CATT, Samsung, Qualcomm Incorporated |
| R3-238153 | On Subsequent CPAC | Lenovo, LG Electronics, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson, NEC |
| R3-238173 | Introduction of Subsequent CPAC | Huawei, ZTE, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, Lenovo, CATT, Samsung, Ericsson |
| 14.2 | Signaling Support for L1/L2 based Inter-Cell Mobility | |
| R3-237140 | LS on CSI resource configuration and on early RACH for LTM | RAN2(Huawei) |
| R3-237147 | Reply LS on beam application time for LTM | RAN4(Ericsson) |
| R3-237163 | TP (BL CR TS 38.401) LTM RS Configuration and Signaling | Nokia, Nokia Shanghai Bell |
| R3-237164 | TP (BL CR TS 38.473) On remaining Stage 3 issues for L1/2 Triggered Mobility (LTM) | Nokia, Nokia Shanghai Bell |
| R3-237170 | (TP to BLCR for TS 38.423) Left issues remaining in LTM | CATT |
| R3-237171 | TP to BLCR for TS 38.473 on LTM | CATT |
| R3-237182 | (TP to Mob_enh2 BL CR TS38.401&TS38.473) Discussion on L1/L2 based Inter-cell Mobility | Samsung |
| R3-237208 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures | Huawei |
| R3-237209 | (TP for L1L2Mob BLCR for TS 38.473): LTM procedure design | Huawei |
| R3-237212 | Remaining issues on TA management for LTM | Fujitsu |
| R3-237234 | (TP to TS38.473 on LTM) Rel-18 LTM Configuration ID, RS Configuration and other | NEC |
| R3-237235 | (TP to TS38.401 on LTM) Updating the serving gNB-DU of other candidate Cell(s) in other candidate gNB-DU(s) | NEC |
| R3-237236 | One or two procedures, consider general Class 2 procedure for information transfer in F1AP | NEC |
| R3-237284 | Further discussion on LTM | NTT DOCOMO INC.. |
| R3-237286 | Signalling Support for LTM | Qualcomm Incorporated |
| R3-237316 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | Ericsson |
| R3-237317 | (TP for LTM BL CR to TS 38.473) Solutions for LTM | Ericsson |
| R3-237415 | Discussion on L1L2 based inter-cell mobility | Lenovo |
| R3-237416 | (TPs to BLCR for TS 38.401 & TS 38.470) Support of L1/L2 based inter-cell mobility | Lenovo |
| R3-237466 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | Google Inc. |
| R3-237467 | (TP for L1L2Mob BLCR for TS 38.401) Resolving FFS in LTM execution | Google Inc. |
| R3-237468 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification after successful cell switch | Google Inc. |
| R3-237620 | (TP for LTM BL CR to TS 38.401/38.423/38.473) Discussion on L1L2 triggered mobility | ZTE |
| R3-237621 | TP for LTM BL CR to TS 38.470 | ZTE, Huawei, CMCC, China Telecom, China Unicom, CATT |
| R3-237645 | Almost complete discussions on LTM (TPs for TS 38.473 and TS 38.401) | LG Electronics Inc. |
| R3-237675 | Discussion on L1L2 based Inter-Cell Mobility | CMCC |
| R3-237819 | CB:#Mobility_LTM | Huawei |
| R3-237980 | (TP for LTM BL CR to TS 38.473) Solutions for LTM | Ericsson, Google, ZTE, CATT, NEC, Nokia, Nokia Shanghai Bell, Huawei, Samsung, LG Electronics Inc. |
| R3-237981 | TP for LTM BL CR to TS 38.470 | ZTE, Huawei, CMCC, China Telecom, China Unicom, CATT, Nokia, Nokia Shanghai Bell, NEC, Google, LG Electronics, Ericsson |
| R3-238005 | (TP to BLCR for TS 38.423) Left issues remaining in LTM | CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics |
| R3-238018 | (TP for L1L2Mob BLCR for TS 38.401): LTM procedure update | Huawei |
| R3-238059 | (TP for L1L2Mob BLCR for TS 38.401): LTM procedure update | Huawei, Nokia, Nokia Shanghai Bell, NEC, Google, ZTE, Samsung, CATT, Ericsson, LG Electronics, Qualcomm Incorporated |
| R3-238060 | (BLCR to 38.423) for LTM | CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics, Huawei, NEC |
| R3-238091 | Introduction of LTM | CMCC, ZTE, Huawei, China Telecom, China Unicom, CATT, Nokia, Nokia Shanghai Bell, NEC, Google, LG Electronics, Ericsson, Lenovo |
| R3-238092 | (BL CR to TS 38.473) Solutions for LTM | Ericsson, Google, ZTE, CATT, NEC, Nokia, Nokia Shanghai Bell, Huawei, Samsung, LG Electronics Inc. |
| R3-238154 | (CR to 38.423) Introduction of L1/L2 triggered mobility | CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics, Huawei, NEC, Lenovo |
| 14.3 | Support CHO in NR-DC | |
| R3-237185 | [TPs to TS38423, TS37483 and TS37340, CHO with MRDC] Completion of the discussions on enhancements for CHO with MR-DC | Nokia, Nokia Shanghai Bell |
| R3-237213 | (TPs to CHO with SCG BL CRs of TS 37.340 and TS 38.423) support of CHO with SCGs | Huawei |
| R3-237287 | CHO with multiple candidate SCGs | Qualcomm Incorporated |
| R3-237307 | (TP for CHO with NR-DC to TS 38.423): Conditional configuration cancel | ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson, Lenovo |
| R3-237308 | (TP for CHO with NR-DC to TS 38.423, TS37.340): Left issue on CHO with multiple SCG | ZTE |
| R3-237309 | (TP for CHO with NR-DC to TS 38.423, TS 37.340): Avoid Multiple Data forwarding Path | ZTE |
| R3-237318 | (TP to TS 38.423 BL CR) CHO with candidate SCG(s) | Ericsson |
| R3-237417 | (TP to BLCR for TS 38.423) CHO in NR-DC | Lenovo |
| R3-237596 | TP to BLCR for 38.423 on CHO with multiple SCGs | CATT |
| R3-237642 | (TP to BLCR TS38.423) Considerations on direct data forwarding | Samsung |
| R3-237643 | (TP to BLCR TS38.423 and TS37.340) Considerations on CHO in NR-DC | Samsung |
| R3-237646 | Complete discussions for the avoidance of multiple data forwarding paths (TP for TS 38.423) | LG Electronics Inc. |
| R3-237647 | Almost complete discussions on CHO with SCGs (TP for TS 38.423) | LG Electronics Inc. |
| R3-237822 | CB:#Mobility_CHO | Samsung |
| R3-237946 | (TP to BLCR TS38.423) Considerations on direct data forwarding | Samsung |
| R3-237954 | (TP to CHO with SCG BL CR of TS 37.340) Direct Data Forwarding | Huawei |
| R3-237978 | (TP for CHO with NR-DC to 37.340): Left issue on CHO with multiple SCG | ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, LG Electronics Inc. |
| R3-237988 | (TP for BL CR for TS 38.423) CHO with SCGs | LG Electronics, Huawei |
| R3-238020 | (TP to BLCR TS38.423) Considerations on direct data forwarding | Samsung |
| R3-238047 | (TP to BLCR TS38.423) Considerations on direct data forwarding | Samsung |
| R3-238049 | (TP to BLCR TS38.423) Considerations on direct data forwarding | Samsung, Huawei, Cybercore, LG Electronics, Ericsson |
| R3-238050 | (TP to CHO with SCG BL CR of TS 37.340) Direct Data Forwarding | Huawei, ZTE, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics |
| R3-238051 | (TP for BL CR for TS 38.423) CHO with SCGs | LG Electronics, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Cybercore |
| 14.4 | Others | |
| R3-237139 | LS on RAN2 progress on subsequent CPAC | RAN2(ZTE) |
| R3-237168 | Reply LS on security for selective SCG activation | RAN2(Nokia) |
| R3-237186 | [TP to BL CR to TS 38.423, S-CPAC] Complete RAN3 part of the S-CPAC solution | Nokia, Nokia Shanghai Bell |
| R3-237214 | (TP to S-CPAC TS 38.423 BL CR) support of subsequent CPAC | Huawei |
| R3-237237 | (TP to TS 38.423 on S-CPAC) S-CPAC related handling of S-SN and Data Forwarding related | NEC |
| R3-237285 | Security issue on S-CPAC | NTT DOCOMO INC.. |
| R3-237288 | Subsequent CPAC in NR-DC | Qualcomm Incorporated |
| R3-237319 | (TP to TS 38.423 BL CR) Support of Subsequent CPAC | Ericsson |
| R3-237418 | Left issues on Subsequent CPAC | Lenovo |
| R3-237566 | Discussion on subsequent CPAC procedures | China Telecommunication |
| R3-237567 | (TP to BL CR of TS 37.483) On support of subsequent CPAC | China Telecommunication |
| R3-237597 | TP to BLCR for 37.483 on subsequent CPAC | CATT |
| R3-237622 | (TP to TS 38.423 and 37.340) Discussion on support of subsequent CPAC | ZTE |
| R3-237623 | [DRAFT] Reply LS on subsequent CPAC | ZTE |
| R3-237644 | (TP to BLCR TS38.401 and TS38.423) Discussion on subsequent CPAC | Samsung |
| R3-237648 | Almost complete discussions on subsequent CPAC (TP for TS 38.423) | LG Electronics Inc. |
| R3-237665 | Discussion on remaining issues for subsequent CPAC | CMCC |
| R3-237736 | Response to R3-237168 and solutions under discussion | LG Electronics Inc. |
| R3-237737 | Reply LS on Security Solution for Selective SCG | SA3(Nokia) |
| R3-237824 | CB:#Mobility_Other | Lenovo |
| R3-237913 | Reply LS on subsequent CPAC | RAN3(ZTE) |
| R3-237949 | Reply LS on subsequent CPAC | RAN3(ZTE) |
| R3-237984 | TP to BLCR for 37.483 on subsequent CPAC | CATT |
| R3-237989 | (TP for BL CR for TS 38.423) S-CPAC | LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell |
| R3-237994 | [TP to BL CR to TS 37.340, S-CPAC] Complete RAN3 part of the S-CPAC solution | Nokia, Nokia Shanghai Bell, Lenovo, Ericsson |
| R3-238022 | (TP to BLCR TS38.401) Subsequent CPAC | Samsung, Nokia, Nokia Shanghai Bell, ZTE, LG Electronics |
| R3-238052 | [TP to BL CR to TS 37.340, S-CPAC] Complete RAN3 part of the S-CPAC solution | Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Google, Huawei, Ericsson, LG Electronics, NEC, CATT, Samsung |
| R3-238053 | (TP for BL CR for TS 38.423) S-CPAC | LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Google, NEC, Huawei, Qualcomm Incorporated, Cybercore |
| R3-238054 | (TP to BLCR for 37.483) on subsequent CPAC | CATT, ZTE,Huawei, NEC, LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-238087 | on subsequent CPAC | CATT, ZTE, Huawei, NEC, LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| 15.1 | General | |
| R3-237043 | (BL CR to TS 38.423) Introduction of NR MBS enhancements | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, CATT, Samsung |
| R3-237044 | (BL CR to 38.410) Update of MBS RAN sharing solution | Qualcomm Inc, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Huawei |
| R3-237045 | (BL CR to 37.483) Introduction of NR MBS enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, Ericsson, CMCC, Samsung |
| R3-237046 | (BL CR to TS 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung |
| R3-237047 | (BL CR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-237048 | (BL CR to TS 38.413) Introduction of NR MBS enhancements | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, Samsung, Ericsson, CMCC, CBN |
| R3-237049 | BLCR to 38.470) Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237050 | (BL CR to TS 38.473) Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| R3-237895 | Summary of Rel-18 MBS offline discussion | CATT |
| R3-237915 | BLCR to 38.470) Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238079 | Introduction of NR MBS enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, Ericsson, CMCC, Samsung |
| R3-238080 | Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung |
| R3-238081 | Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-238082 | Introduction of NR MBS enhancements | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, Samsung, Ericsson, CMCC, CBN |
| R3-238083 | Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238084 | Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| R3-238155 | Introduction of NR MBS enhancements | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, CATT, Samsung |
| R3-238156 | (CR to 38.410) Update of MBS RAN sharing solution | Qualcomm Inc, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Huawei |
| 15.2 | Support for MBS reception in RAN sharing scenarios | |
| R3-237161 | Leftover issues on network sharing for MBS Broadcast | ZTE |
| R3-237215 | (TPs to MBS BL CRs of TS 38.401, 38.413, 38.470, 38.473, 37.483) MBS reception in RAN sharing scenario | Huawei, CBN |
| R3-237264 | Support of MBS in RAN sharing scenarios | Qualcomm Incorporated |
| R3-237272 | (TP for TS 38.413, TS 38.473, TS 38.470) Resolution of RAN sharing open points | Nokia, Nokia Shanghai Bell |
| R3-237334 | (TP to BL CR for 37.483, 38.473) Introducing MBS RAN sharing | Samsung |
| R3-237396 | Finalising Support for MBS Reception in RAN Sharing Scenarios | Ericsson |
| R3-237557 | (TP for BLCRs)Discussion on efficient MBS reception in RAN sharing scenario | CATT,CBN |
| R3-237861 | (TP to MBS BL CRs for TS 38.300) Support of MBS reception in RAN sharing scenario | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Huawei, Samsung |
| R3-237863 | (TP to MBS BL CRs for TS 38.401) Support of MBS reception in RAN sharing scenario | ZTE, CATT, Huawei, Ericsson, Lenovo, Samsung, Qualcomm, CMCC, Nokia, Nokia Shanghai Bell |
| R3-237864 | (TP to MBS BL CRs for TS 38.413) Support of MBS reception in RAN sharing scenario | Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson |
| R3-237865 | (TP to MBS BL CRs for TS 38.470) Support of MBS reception in RAN sharing scenario | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-237866 | (TP to MBS BL CRs for TS 38.473) Support of MBS reception in RAN sharing scenario | Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237867 | (TP to MBS BL CRs for TS 37.483) Support of MBS reception in RAN sharing scenario | Samsung |
| R3-237870 | (TP to MBS BL CRs for TS 38.423) Support of MBS reception in RAN sharing scenario | CMCC |
| R3-237985 | (TP to MBS BL CRs for TS 38.401) Introduction of general description on RAN sharing for MBS | CMCC |
| R3-238014 | (TP to MBS BL CRs for TS 37.483) Support of MBS reception in RAN sharing scenario | Samsung, Nokia, Nokia Shanghai Bell, Ericsson |
| 15.3 | Support for RRC_INACTIVE state | |
| R3-237152 | LS on Providing MBS assistance information from SMF towards NG-RAN node during Xn handover | SA2(Nokia) |
| R3-237162 | (TPs to BLCRs) Flowchart for multicast RRC_INACTIVE reception | ZTE |
| R3-237216 | (TPs to MBS BL CRs of TS 38.300, 38.413, 38.473, 38.470) Multicast Reception for RRC_INACTIVE state UEs | Huawei, CBN |
| R3-237263 | Enhancements to support Multicast reception by UEs in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-237273 | (TP for TS 38.423, TS 38.300, TS 38.473) Resolution of open points for RRC Inactive mode reception | Nokia, Nokia Shanghai Bell |
| R3-237274 | Reply LS on providing MBS assistance information from SMF towards NG-RAN node during Xn handover | Nokia, Nokia Shanghai Bell |
| R3-237335 | (TP for BL CR for TS 38.473) Introducing MBS reception by inactive state UE | Samsung |
| R3-237397 | Finalising Support for RRC_INACTIVE state | Ericsson |
| R3-237419 | Discussion on multicast reception in RRC_INACTIVE | Lenovo |
| R3-237558 | (TP for BLCRs)Discussion on Multicast over Inactive | CATT,CBN |
| R3-237868 | (TP to MBS BL CRs for TS 38.473) Support of MBS reception in RRC_Inactive state | Ericsson |
| R3-237869 | (TP to MBS BL CRs for TS 38.470) Support of MBS reception in RRC_Inactive state | CATT |
| R3-238013 | (TP to MBS BL CRs for TS 38.473) Support of MBS reception in RRC_Inactive state | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT, Lenove, Samsung, Qualcomm |
| 16.1 | General | |
| R3-237051 | (BLCR to 38.300) Support of SL relay enhancements | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE, Huawei |
| R3-237052 | (BLCR to 38.413) Support for NR Sidelink Relay Enhancements | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei |
| R3-237053 | (BLCR to 38.423) Support NR Sidelink Relay Enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC |
| R3-237054 | (BLCR to 38.470) Support of NR SL relay enhancements | ZTE, CAICT, China Telecom, CATT, LG Electronics, Ericsson, Huawei |
| R3-237055 | (BLCR to 38.401) Introduction of NR SL relay enhancements | LG Electronics, Huawei, Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237056 | (BL CR to 37.483) Introduce new indication for proactive data forwarding | Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-237057 | (BLCR to 38.473) Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-237806 | Summary of AI 16 on SL Relay Enhancement | LG Electronics |
| R3-237828 | (BL CR to 37.483) Support of NR SL relay enhancements | Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-238112 | Support of NR SL relay enhancements | Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, Ericsson |
| R3-238113 | Support of SL relay enhancements | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE, Huawei, NEC |
| R3-238114 | Introduction of NR SL relay enhancements | LG Electronics, Huawei, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, NEC, ZTE |
| R3-238115 | Support for NR Sidelink Relay Enhancements | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei, NEC |
| R3-238116 | Support NR Sidelink Relay Enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCCNEC |
| R3-238117 | Support of NR SL relay enhancements | ZTE, CAICT, China Telecom, CATT, LG Electronics, Ericsson, Huawei, NEC, Nokia, Nokia Shanghai Bell |
| R3-238118 | Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTENEC |
| 16.3 | Support Service Continuity Enhancements | |
| R3-237254 | (TP for BLCR 38.413, 38.423, 38.401, 37.483) Inter-gNB mobility | Huawei |
| R3-237282 | (TPs for SL relay to TS 37.483 and 38.401)Remaining issues on service continuity for SL relay | ZTE |
| R3-237297 | (TP to BL CR for 38.300) Corrections on BL CR to 38.300 | LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, NEC, CATT, CMCC, Huawei |
| R3-237299 | (TPs for 38.401, 37.483, 38.413, 38.423) Remaining open issues for service continuity enhancement | LG Electronics |
| R3-237320 | (TP for SL Relay BL CR to TS 37.483) Lossless DL data delivery | Ericsson |
| R3-237434 | (TP for TS37.483 BL CR) Discussion on Support Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-237572 | Remaining issues on SL relay service continuity | China Telecommunication |
| R3-237589 | (TP for SL relay 38.401 and 37.483) Discussion on Support Service Continuity Enhancements | CATT |
| R3-237671 | (TP to TS 38.300) SL relay service continuity | CMCC |
| R3-237807 | (TP for SL Relay BLCR to TS 38.413) Support of service continuity enhancement | LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237820 | (TP for BLCR 38.423) Inter-gNB mobility | Huawei, LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237909 | (TP for SL relay BLCR to TS 38.401) Support of service continuity enhancement | ZTE, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-237951 | (TP for BL CR for TS37.483) Update on the Indirect Path Indication | Nokia, Nokia Shanghai Bell |
| 16.4 | Multi-path Support | |
| R3-237246 | Discussion on remaining issue of multi-path relay | NEC |
| R3-237255 | (TP for BLCR 38.473) Multi-path relay | Huawei |
| R3-237283 | (TPs for SL relay to TS 38.473 and 38.470)Remaining issues on multi-path relay | ZTE |
| R3-237298 | (TPs for 38.401, 38.473, 38.470) Remaining open issues for multi-path support | LG Electronics |
| R3-237321 | (TPs for SL Relay to TS 38.401 and TS 38.473) Multi-path for Sidelink Relay | Ericsson |
| R3-237365 | (TP for TS38.401 BL CR) Inter-DU direct path addition on top of indirect path | ZTE, NEC, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Huawei, CATT |
| R3-237435 | (TP for TS38.474 BL CR) discussion on the support for multi-path | Nokia, Nokia Shanghai Bell |
| R3-237573 | Discussion on multi-path for sidelink relay | China Telecommunication |
| R3-237590 | (TP for SL relay 38.401) Discussion on Multi-path Support for SL relay | CATT |
| R3-237634 | Leftovers for SL relay multipath | Samsung |
| R3-237635 | (TP to BL CR 38.473) SL relay multi-path | Samsung |
| R3-237672 | (TP to TS 38.401 and TS 38.473) Discussion on multi path relay | CMCC |
| R3-237808 | (TP for SL Relay BLCR to TS 38.401) Support of multi-path relay | LG Electronics, Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237814 | (TP for TS38.401 BL CR) Inter-DU direct path addition on top of indirect path | ZTE, NEC, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Huawei, CATT |
| R3-237821 | (TP for BLCR 38.473) Multi-path relay | Huawei, LG Electronics, Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R3-237829 | CB:#SLRelay | LGE |
| R3-237974 | (TP for SL Relay to TS 38.470) Multi-path for Sidelink Relay | Ericsson, LG Electronics, ZTE, Nokia, Nokia Shanghai Bell |
| 17.1 | General | |
| R3-237058 | (BLCR to 38.300) Stage 2 BL CR for NR NTN | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-237059 | (BLCR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-237060 | (BLCR to 38.423) BL CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-237697 | (BLCR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-238157 | Stage 2 CR for NR NTN | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, NEC |
| R3-238158 | CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC, Qualcomm Incorporated, NEC |
| R3-238159 | CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated, NEC |
| 17.3 | Network verified UE location | |
| R3-237138 | LS on NW verified UE location failure during cell change | RAN2(Qualcomm) |
| R3-237244 | The discussion on location verification of NTN | NEC |
| R3-237260 | Discussion on remaining issues in Network Verified UE Location | Qualcomm Incorporated |
| R3-237300 | Further discussion on OAM requirements for UE location verification | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-237301 | (TP to BL CR for TS 38.455) Positioning support for NR NTN UE location | CATT |
| R3-237338 | Discussion on remaining issues for network verified UE location | ZTE |
| R3-237368 | (TP BL 38.300) OAM Requirements for UE Location Verification | Huawei, Ericsson, CATT |
| R3-237369 | (TP to 38.305) Mapped cell Id usage for UE disambiguation in multi-RTT | Huawei, Thales, Ericsson |
| R3-237370 | Mapped Cell Id Introduction for E-CID and NR NTN | Huawei, Thales, Ericsson |
| R3-237371 | Discussion on Altitude for the NTN TRP | Huawei, Thales, Ericsson |
| R3-237372 | (TP BL 38.455) NTN Access Point Position | Huawei, Thales, Ericsson |
| R3-237373 | LS on Altitude for the Access Point | Huawei, Thales, Ericsson |
| R3-237375 | Discussion on NW verified UE location failure during cell change and reply LS | Huawei, Ericsson, Thales |
| R3-237420 | On NTN NW verified UE location | Lenovo |
| R3-237428 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei |
| R3-237436 | (TP for TS 38.455) Support UE location verification in NR NTN | Nokia, Nokia Shanghai Bell |
| R3-237443 | Remaining Issues on UE Location Verification | Ericsson, Thales, Huawei |
| R3-237445 | UE Location Verification Failure During Cell Change | Ericsson, Huawei |
| R3-237454 | Discussion on E-CID method for NTN | THALES, Huawei, Ericsson |
| R3-237571 | On NTN network verified UE location | China Telecommunication |
| R3-237636 | Leftovers for UE location verification | Samsung |
| R3-238023 | Summary of Offline Discussion – NR NTN UE Location Verification | Ericsson |
| R3-238024 | Reply LS on NW verified UE location failure during cell change | RAN3(Qualcomm) |
| R3-238025 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei, ZTE |
| R3-238026 | (TP BL 38.300) OAM Requirements for UE Location Verification | Huawei, Ericsson, CATT |
| R3-238027 | [Draft] LS on OAM requirements for UE location verification | CATT |
| R3-238028 | Introduction of Common TA for NR NTN | Qualcomm, Ericsson |
| R3-238055 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238056 | LS on OAM requirements for UE location verification | RAN3(CATT) |
| R3-238057 | (BLCR to 38.455) Introduction of Common TA Parameters for NR NTN | Qualcomm, Ericsson |
| R3-238160 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-238161 | Introduction of Common TA Parameters for NR NTN | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, NEC, Huawei, ZTE |
| 18.1 | General | |
| R3-237061 | (BL CR to 36.300) IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-237062 | (BLCR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-237063 | (BLCR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-237702 | (BLCR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-237942 | (BLCR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-237943 | (BLCR to 36.300) IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-238162 | IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE, Qualcomm Incorporated |
| R3-238163 | IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-238164 | IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| 18.2 | Support discontinuous coverage | |
| R3-237166 | LS on UE Location Information for NB-IoT NTN | RAN2(Inmarsat) |
| R3-237176 | (TP to BL CR for TS 36.455, 36.300, 36.305) supporting of E-CID | CATT |
| R3-237339 | Discussion on remaining issue for IoT NTN | ZTE |
| R3-237374 | E-CID for Network UE location Verification | Huawei |
| R3-237426 | Mapped Cell ID Introduction for E-CID and IoT NTN | Ericsson, Huawei, Thales |
| R3-237427 | (TP to BL CR for TS 36.455) NTN Access Point Position | Ericsson, Huawei, Thales |
| R3-237429 | UE Location Verification and IoT NTN | Ericsson LM |
| R3-237437 | (TP for TS 36.413 BL CR) Discussion on remaining issues to support IoT NTN | Nokia, Nokia Shanghai Bell |
| 19.1 | General | |
| R3-237064 | Introduction of Aerial authorization information | Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-237065 | (BLCR to 38.423) NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| R3-237210 | Draft CR to 38.300 on NR support for UAV | Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC |
| R3-238119 | Draft CR to 38.300 on NR support for UAV | Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC |
| R3-238120 | Introduction of Aerial authorization information and A2X services support | Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-238121 | NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung, CMCC, NEC |
| 19.2 | Support Subscription-based Aerial-UE Identification | |
| R3-237177 | (TP to BL CR for TS 38.413)Support of A2X communication | CATT |
| R3-237178 | TP (BL CR TS 38.300) Stage 2 corrections for NR support for UAV | Nokia, Nokia Shanghai Bell |
| R3-237382 | (TPs for UAV BL CRs for TS 38.423, TS 38.413 and TS 38.473) Remaining open issues for NR UAV | Huawei |
| R3-237519 | Text Proposal to NGAP and XnAP Baseline CRs on NR support for UAV | Ericsson |
| R3-237713 | Discussion on UAV left issues | ZTE, CMCC, China Telecom |
| R3-237714 | TP to TS 38.413 BLCR for A2X communication supporting and flightpath modification | ZTE, CMCC, China Telecom |
| R3-237715 | TP to TS 38.423 BLCR for A2X communication supporting and flightpath information modification | ZTE, CMCC,CATT, China Telecom |
| R3-237873 | CB:#R18UAV | ZTE |
| R3-237958 | Reply LS on flightpath information forwarding for UAV | RAN2(ZTE) |
| R3-237991 | (TP for TS 38.473) A2X service support in F1AP | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237998 | (TP for BL CR 38.413) Support of A2X communication | CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson |
| R3-237999 | TP to TS 38.423 BLCR for A2X service supporting and flightpath information modification | ZTE, CMCC, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-238000 | LS to SA2 and RAN2 for RAN3 progress on NR UAV | Ericsson |
| R3-238012 | TP (BL CR TS 38.300) Stage 2 corrections for NR support for UAV | Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-238019 | LS on RAN3 progress for UAV flight path information handling and A2X service support | RAN3(Ericsson) |
| R3-238122 | A2X communication services support in F1AP | ZTE, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, NEC |
| 20.1 | General | |
| R3-237066 | (BLCR to 38.473) Introduction on MT-SDT | China Telecom, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-237067 | (BLCR to 38.420) Introduction on MT-SDT | Lenovo, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237068 | (BL CR to TS 37.483) Introduction of MT-SDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics |
| R3-237069 | (BL CR to 38.300) Introduction on MT-SDT | ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics |
| R3-237070 | (BLCR to 38.401) Introduction on MT-SDT | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics |
| R3-237071 | (BLCR to 37.480) Introduction on MT-SDT | LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-237072 | (BLCR to 38.423) Introduction of MT-SDT | Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo |
| R3-237874 | Introduction on MT-SDT | China Telecom, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-237875 | Introduction on MT-SDT | Lenovo, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237876 | Introduction of MT-SDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics |
| R3-237877 | Introduction on MT-SDT | ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics |
| R3-237878 | Introduction on MT-SDT | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics |
| R3-237879 | (CR to 37.480) Introduction on MT-SDT | LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-237880 | (CR to TS 38.423) Introduction of MT-SDT | Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo |
| 21.1 | General | |
| R3-237073 | (BL CR to TS 38.300) Introduction of NR Redcap Enhancement | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| R3-237074 | (BLCR to 38.410) Introduction of NR Redcap Enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237075 | Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-237076 | (BLCR to 38.413) Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237077 | (BLCR to 38.473) Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-237529 | WI work plan for Rel-18 RedCap | Rapporteur (Ericsson) |
| R3-237771 | (BLCR to 38.473) Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-238108 | Introduction of NR RedCap Enhancement | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Qualcomm Incorporated, Huawei |
| R3-238109 | Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated |
| R3-238111 | Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-238165 | Introduction of NR Redcap Enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238166 | Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT, Xiaomi, Qualcomm Inc. |
| R3-238174 | Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| 21.2 | Support Enhanced eDRX in RRC_INACTIVE | |
| R3-237151 | Reply LS on INACTIVE eDRX above 10.24sec and SDT | SA2(Intel) |
| R3-237228 | (TP to BLCR for TS 38.413) Further discussion on long eDRX support for RRC_INACTIVE UE | Huawei |
| R3-237229 | (TP to BLCR for TS 38.300) Further discussion on long eDRX support for RRC_INACTIVE UE | Huawei |
| R3-237230 | (TP to BLCR for TS 38.473) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication |
| R3-237258 | Discussion on MT-SDT for RedCap | Qualcomm Incorporated |
| R3-237275 | (TP for TS 38.300) Finalization of eDRX for RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
| R3-237276 | (TP for TS 38.413) Finalization of eDRX for RRC_INACTIVE for NGAP | Nokia, Nokia Shanghai Bell |
| R3-237289 | (TP to BLCR for TS 38.470) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication |
| R3-237310 | (TP to 38.423, 38.300) Left issues on NR Redcap enhancement | ZTE |
| R3-237311 | Discussion on NR Redcap enhancement with MT-SDT | ZTE |
| R3-237530 | Finalizing the Rel-18 eRedCap topics | Ericsson |
| R3-237531 | (TP to TS 38.413 BL CR): Addition of data size information options for MT-SDT paging with long enhanced eDRX | Ericsson, Xiaomi, Qualcomm Inc. |
| R3-237532 | (TP to TS 38.300 BL CR): Addition of partial anchor relocation limitation for NG-RAN node when selecting eDRX longer than 10.24 seconds and activating HLCOM | Ericsson, Xiaomi, Qualcomm Inc. |
| R3-237533 | (TP to NGAP BL CR): Fix of stage 3 issues to NGAP | Ericsson, Qualcomm Inc., ZTE, CATT |
| R3-237534 | (TP to F1AP BL CR): Fix of stage 3 issues to F1AP | Ericsson, ZTE, CATT |
| R3-237535 | LS on Rel-18 eRedcap WI completion | Ericsson |
| R3-237754 | Proposed summary of proposals for eRedCap online session | Ericsson |
| R3-237773 | CB:# eRedcap | Ericsson |
| R3-237797 | Reply LS on INACTIVE eDRX above 10.24sec and SDT | CT4(Ericsson) |
| R3-237815 | (TP to NGAP BL CR): Fix of stage 3 issues to NGAP | Ericsson, Qualcomm Inc., ZTE, CATT, Nokia, Nokia Shanghai Bell, China Telecom, Huawei |
| R3-237816 | (TP to F1AP BL CR): Fix of stage 3 issues to F1AP | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-237817 | (TP for TS 38.300) Fix of stage 2 issues | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-237818 | (TP to BLCR for TS 38.470) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication, Ericsson, ZTE |
| R3-238110 | Introduction of NR RedCap Enhancement | Qualcomm Incorporated, Huawei, China Unicom, China Telecommunication, Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| 22.1 | General | |
| R3-237078 | (BLCR) Support of Network-Controlled Repeater | Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung, NEC, China Telecom, ZTE |
| R3-237079 | (BLCR) Support of Network-Controlled Repeater | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Samsung, China Telecom, ZTE, NEC |
| R3-237080 | (BLCR) Network-Controlled Repeaters Authorization | Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237081 | (BL CR to 38.300) BL CR for Network Controlled Repeater management | ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237881 | Support of Network-Controlled Repeater | Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung, NEC, China Telecom, ZTE |
| R3-237882 | Support of Network-Controlled Repeater | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Samsung, China Telecom, ZTE, NEC |
| R3-237883 | Network-Controlled Repeaters Authorization | Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237884 | Introduction of Network controlled repeater | ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| 23.1 | General | |
| R3-237082 | (BL CR to TS 38.305) Support of NR Positioning Enhancements | Nokia, Nokia Shanghai Bell, CATT, Huawei, Ericsson, Xiaomi, ZTE, Samsung |
| R3-237083 | (BL CR to 38.413) Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237084 | (BL CR to 38.423) Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237085 | (BL CR to 38.455) Support of NR Positioning Enhancements | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi, Samsung |
| R3-237086 | (BL CR to TS 38.470) Support of NR Positioning Enhancements | Samsung, Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi |
| R3-237087 | (BL CR to TS 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237302 | Work Plan for Rel-18 WI on Expanded and Improved NR Positioning | CATT |
| R3-237823 | SoD on Positioning R18 | CATT |
| R3-237830 | Reply LS on CPP | RAN1 |
| R3-237831 | Reply LS on SRS and PRS bandwidth aggregation for positioning | RAN1 |
| R3-237832 | Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | RAN1 |
| R3-237858 | (BL CR to 38.455) Support of NR Positioning Enhancements | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi, Samsung, China Telecom |
| R3-237859 | (BL CR to TS 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237916 | SoD on Positioning R18 | CATT |
| R3-238097 | (BL CR to TS 38.305) Support of NR Positioning Enhancements | Nokia, Nokia Shanghai Bell, CATT, Huawei, Ericsson, Xiaomi, ZTE, Samsung |
| R3-238098 | (BL CR to 38.413) Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238099 | (BL CR to 38.423) Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238100 | (BL CR to 38.455) Support of NR Positioning Enhancements | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi, Samsung, China Telecom |
| R3-238101 | (BL CR to TS 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell, Xiaomi, Samsung |
| 23.2.1 | Sidelink Positioning | |
| R3-237150 | LS on SL positioning and carrier phase positioning measurements | RAN4(CATT) |
| R3-237387 | (TP to TS 38.413) Clarification on Ranging and Sidelink Positioning Service Information | Xiaomi, Ericsson, Samsung |
| R3-237388 | (draft LS to RAN2) Support of SL positioning | Xiaomi |
| R3-237536 | (TP to TS 38.423) Clarification on Ranging and Sidelink Positioning Service Information | Ericsson, Xiaomi, Samsung |
| R3-237537 | Discussion on SL positioning in network coverage mode and NRPPa impacts + LS to RAN2 | Ericsson |
| R3-237639 | (TP to TS 38.473) Clarification on Ranging and Sidelink Positioning Service Information | Samsung, Xiaomi, Ericsson |
| R3-237860 | LS on LMF involvement in SL-PRS resource allocation | RAN3(Xiaomi) |
| 23.2.2 | LPHAP | |
| R3-237136 | LS on PRS bandwidth aggregation | RAN1(ZTE) |
| R3-237148 | Reply LS to RAN1 on SRS and PRS bandwidth aggregation for positioning | RAN4(ZTE) |
| R3-237149 | LS on report mapping for positioning measurements with PRS_SRS bandwidth aggregation | RAN4(Ericsson) |
| R3-237303 | (TP for BL CR to TS 38.455, 38.423, 38.305) on support of LPHAP | CATT |
| R3-237366 | (TP BL 38.xxx) Remaining Issues on LPHAP | Huawei |
| R3-237389 | (TP for TS 38.455) Support of LPHAP | Xiaomi |
| R3-237399 | (TP for TS 38.455 BL CR) Further details for LPHAP | Nokia, Nokia Shanghai Bell |
| R3-237696 | Further discussion on LPHAP impacts | ZTE |
| R3-237917 | (TP for BL CR to TS 38.305) on support of LPHAP | CATT, Xiaomi, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-237918 | (TP for BL CR to TS 38.455) on support of LPHAP | Nokia, Nokia Shanghai Bell, CATT, Xiaomi |
| R3-237919 | (TP BL 38.473) Remaining Issues on LPHAP | Huawei, CATT, ZTE, Xiaomi, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| 23.2.3 | Others | |
| R3-237141 | LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | RAN2(Nokia) |
| R3-237144 | Reply LS on R1-2308644 for CPP | RAN2(CATT) |
| R3-237304 | (TP for BL CR to TS 38.455) More details on support of BW aggregation | CATT |
| R3-237367 | (TP BL 38.xxx) Discussion on CPP, Bandwidth Aggregation and Redcap Postioning | Huawei |
| R3-237400 | (TP for TS 38.455 BL CR) Resolution of open issues for accuracy enhancements | Nokia, Nokia Shanghai Bell |
| R3-237538 | Discussion on SRS BW aggregation and RedCap positioning | Ericsson |
| R3-237640 | Remaining issues on positioning others | Samsung |
| R3-237698 | (TP for 38.455 & 38.473 BLCR) Discussion on PRS&SRS Band Aggregation | ZTE |
| R3-237920 | (TP for BL CR to TS 38.455) on support of BW aggregation and CPP | Ericsson, CATT, ZTE, Huawei, Xiaomi, Nokia, Nokia Shanghai Bell, Samsung |
| R3-237921 | (TP for BL CR to TS 38.473) on support of BW aggregation and CPP | ZTE, CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi |
| 24.1 | General | |
| R3-237088 | (BLCR to 38.473) Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| R3-237089 | (BL CR to 38.300) Introduction of Network Energy Saving | ZTE, Ericsson |
| R3-237090 | (BLCR to 38.423) Network energy saving techniques | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-237091 | (BL CR to 38.470) Network energy saving techniques | Qualcomm |
| R3-237225 | WI Work plan for R18 network energy savings | Huawei |
| R3-237862 | (BLCR to 38.473) Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| R3-238064 | Introduction of Network Energy Saving | ZTE, Ericsson, Samsung, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, CATT |
| R3-238066 | Introduction of Network Energy Saving | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-238067 | Network energy saving techniques | Qualcomm, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-238068 | Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel, Nokia, Nokia Shanghai Bell |
| 24.2 | Support Network Energy Savings | |
| R3-237145 | Reply LS on paging | RAN2(Huawei) |
| R3-237226 | (TP to BLCR for TS 38.473, 38.401, 38.470 and 38.300) Finalizing network energy saving techniques | Huawei, Deutsche Telekom |
| R3-237227 | (TP to BLCR for TS 38.423) Finalizing network energy saving techniques | Huawei |
| R3-237327 | Discussion on network energy saving | Samsung |
| R3-237328 | Introduction of Network Energy Saving for Paging IDLE UE | Samsung |
| R3-237398 | (TP to BL CR for TS 38.423) Cell DTRX in Network Energy Saving | Ericsson |
| R3-237451 | (TP to TS 38.423) Discussion on Paging in Subset of Beams and Inter-node Cell DTX/DRX Configuration | Nokia, Nokia Shanghai Bell |
| R3-237452 | (TP to TS 38.473) Beam deactivation decision and signalling for energy saving | Nokia, Nokia Shanghai Bell |
| R3-237460 | Open issues on NES techniques | Qualcomm Incorporated |
| R3-237516 | Introduction of Network Energy Saving | Ericsson |
| R3-237618 | (TP to NES BL CR for TS38.423) Discussion on inter-node beam activation and cell DTXDRX for NES | CATT |
| R3-237619 | TP to NES BLCR for TS 38.420 | CATT |
| R3-237660 | Discussion on network energy saving | ZTE |
| R3-237661 | TP to BL CR of XnAP for Cell DTX-DRX | ZTE |
| R3-237662 | TP to BLCR of 38.300 for network energy saving | ZTE, Samsung, Ericsson, Qualcomm Incorporated |
| R3-237733 | Response to R3-237226 F1AP enhancements for NES CHO | Qualcomm Technologies Int |
| R3-237795 | Proposed summary for Network Energy saving online session | Huawei |
| R3-237872 | CB:#R18ES | Huawei |
| R3-237890 | (TP to BLCR for TS 38.470) Finalizing network energy saving techniques | Huawei, Deutsche Telekom, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237891 | (TP to BLCR for TS 38.423) Finalizing network energy saving techniques | Huawei |
| R3-237892 | (TP to BLCR for TS 38.300) Finalizing network energy saving techniques | ZTE, Samsung, Ericsson, Qualcomm Incorporated, Huawei |
| R3-237893 | (TP to BLCR for TS 38.420) Finalizing network energy saving techniques | CATT |
| R3-237894 | (TP to BLCR for TS 38.473) Finalizing network energy saving techniques | Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-238058 | (TP to BLCR for TS 38.300) Finalizing network energy saving techniques | ZTE, Samsung, Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, CATT |
| R3-238065 | Network energy saving enhancements | CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| 25.1 | General | |
| R3-237092 | (BL CR to 38.300) for XR Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Samsung |
| R3-237093 | (BL CR to 38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom, ZTE |
| R3-237094 | (XR BL CR to TS 38.423) Introduction of XR enhancement | Ericsson, ZTE, Qualcomm Inc., Nokia, Nokia Shanghai Bell |
| R3-237095 | (BL CR to 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237096 | (BLCR to 37.483) Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237097 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc |
| R3-237098 | (BL CR to 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc |
| R3-237340 | (BL CR to 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc |
| R3-237774 | (XR BL CR to TS 38.423) Introduction of XR enhancement | Ericsson, ZTE, Qualcomm Inc., Nokia, Nokia Shanghai Bell, China Telecom |
| R3-237775 | (BL CR to 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237776 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc |
| R3-237777 | (BL CR to 38.300) for XR Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Samsung |
| R3-238123 | Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238124 | CR to TS 38.300 for XR Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Samsung, Xiaomi |
| R3-238126 | (CR to 38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom, ZTE |
| R3-238127 | Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo |
| R3-238129 | Introduction of XR enhancement | Ericsson, ZTE, Qualcomm Inc., Nokia, Nokia Shanghai Bell, China Telecom, Huawei, CMCC, Xiaomi, Lenovo, Samsung, LGE |
| R3-238130 | Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc, Lenovo |
| R3-238132 | Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| 25.2.1 | PDU Set Handling | |
| R3-237261 | XR Enhancements for PDU Set Handling | Qualcomm Incorporated |
| R3-237331 | (TP to BL CR for 38.413, 37.483, 38.423) Discussion on the support of PDU Set handling | Samsung |
| R3-237332 | (TP to BL CR for TS 37.483) Addition of UL PDU Set QoS parameters | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc., Xiaomi, China Telecom |
| R3-237359 | (TP for NR_XR_enh BL CRs for TS38.413/38.423/38.473/38.415):PDU set handling for support NR XR | Huawei |
| R3-237390 | (TP for TS 38.423) Introduction of Direction Information for PDU Set QoS Parameters | Xiaomi, Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Samsung, China Telecom |
| R3-237391 | (TP for TS 38.300) Non-homogenous support of PDU set based QoS handling in NG-RAN | Xiaomi, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237392 | (TPs for 38.473, 37.483 and 38.413) PDU set based QoS handling for XR | Xiaomi |
| R3-237421 | (TP to BLCR for TS 38.415) User Plane Protocol for PDU Set Information | Lenovo, Ericsson |
| R3-237438 | (TP for TS 38.413 BL CR) Discussion on support for PDU Set based QoS handling | Nokia, Nokia Shanghai Bell |
| R3-237539 | (TP to F1-AP BL CR): introduction of UL UE XR Traffic assistance Information | Ericsson |
| R3-237540 | (TP to NG-AP BL CR): introduction of Direction Information for PDU Set QoS Parameters | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, China Telecom |
| R3-237541 | LS on defining new GTP-U Extension Header for PDU Set Information | Ericsson, lenovo |
| R3-237591 | (TP for XR 38.415 and 38.425) Discussion on PDU set handling for XR | CATT |
| R3-237624 | Discussion on support of PDU Set Handling | ZTE |
| R3-237625 | (TP to BL CR TS 38.415) Support for XR UP design using existing frame | ZTE, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| R3-237626 | (TP to BL CR TS 38.415) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom |
| R3-237627 | (TP to BL CR TS 38.410) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom |
| R3-237628 | (TP to BL CR TS 38.420) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom |
| R3-237629 | (TP to BL CR TS 38.470) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom |
| R3-237633 | Discussion on XR Enhancement in Split Architecture | China Telecom |
| R3-237677 | (TP for TS38.425) Support for XR PDU Set Handling | CMCC, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-237678 | Discussion on PDU Set handling | CMCC |
| R3-237778 | CB:#18R18XR1_PDUSet | Nokia |
| R3-237840 | (TP for TS 38.423 BL CR) support for PDU Set based QoS handling | Huawei, Ericsson, ZTE, Lenovo, Samsung, Nokia, Nokia Shanghai Bell, LGE |
| R3-237841 | (TP for TS 38.413 BL CR) support for PDU Set based QoS handling | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung |
| R3-237842 | (TP for TS 37.483 BL CR) support for PDU Set based QoS handling | Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Lenovo |
| R3-237843 | (TP for TS 38.300 BL) Support for NR XR | Xiaomi, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson, Qualcomm Inc. |
| R3-237844 | (TP for BLCR to TS 38.415) On User Plane Protocol for PDU Set Information | Lenovo, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-237845 | LS on defining new GTP-U Extension Header for PDU Set related information | RAN3(Ericsson) |
| R3-237846 | (TP to BL CR TS 38.410) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-237847 | (TP to BL CR TS 38.470) Support for XR UP design using new container | ZTE, Ericsson, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-237848 | (TP for TS38.425) Support for XR PDU Set Handling | CMCC, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-237849 | (TP for TS38.420) Support for XR PDU Set Handling | CMCC, Lenovo, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237850 | (TP to BL CR TS 38.473) Support for UL jitter | Xiaomi |
| R3-237851 | (TP to BL CR TS 38.473) Support for N6 jitter | Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell |
| R3-238032 | (TP for TS 38.300 BL) Support for NR XR | Xiaomi, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson, Qualcomm Inc., Samsung |
| R3-238125 | Support for XR UP design using new container | China Unicom, ZTE, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-238128 | Support for XR PDU Set Handling | Lenovo, Nokia, Nokia Shanghai Bell, ZTE |
| R3-238131 | Support for XR UP design using new container | China Telecom, ZTE, Ericsson, China Unicom, Nokia, Nokia Shanghai Bell, Lenovo |
| 25.2.2 | ECN Marking and others | |
| R3-237262 | RAN Signaling Enhancements for Congestion Management | Qualcomm Incorporated |
| R3-237333 | (TP to BL CR for 38.413, 38.423, 37.483) Introducing enhancement for NR XR ECN and discarding | Samsung |
| R3-237360 | (TP for NR_XR_enh BL CRs forTS 38.413/38.423/37.483/38.473/ 38.415/38.425): Discussion on open issues for support NR XR | Huawei |
| R3-237394 | Discussion on open issues for ECN marking and others | LG Electronics Inc. |
| R3-237422 | On ECN Marking, PDCP Discard and Data Forwarding | Lenovo |
| R3-237439 | Discussion on ECN marking and PDU Set Discard for NR XR | Nokia, Nokia Shanghai Bell |
| R3-237440 | TP for TS38.413 BL CR | Nokia, Nokia Shanghai Bell, CMCC, ZTE |
| R3-237441 | TP for TS38.423 BL CR | Nokia, Nokia Shanghai Bell, CMCC, ZTE |
| R3-237442 | TP for TS38.473 BL CR | Nokia, Nokia Shanghai Bell, CMCC, ZTE |
| R3-237470 | Support for L4S in NG-RAN | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237471 | (TP for NR_XR_enh BL CR for TS37.483) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237472 | (TP for NR_XR_enh BL CR for TS38.413) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237473 | (TP for NR_XR_enh BL CR for TS38.415) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237474 | (TP for NR_XR_enh BL CR for TS38.423) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237475 | (TP for NR_XR_enh BL CR for TS38.425) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237476 | (TP for NR_XR_enh BL CR for TS38.473) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, Verizon Wireless, Telstra, Qualcomm |
| R3-237592 | Discussion on ECN Marking and others for XR | CATT |
| R3-237630 | Discussion on ECN marking and PDU Set discard | ZTE |
| R3-237631 | (TP to BL CR TS 38.415) support for ECN Marking | ZTE, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| R3-237632 | Enhancement for PDU Set Discard Operation | China Telecom |
| R3-237679 | (TP for TS38.425) Support for ECN marking | CMCC, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237680 | Discussion on ECN marking and congestion exposure | CMCC |
| R3-237781 | CB:#R18XR2_ECNMarking | Ericsson |
| R3-237922 | (TP to BL CR TS 38.415) support for ECN Marking | ZTE, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC, Ericsson |
| R3-237936 | (TP to BL CR for 37.483) Support for ECN Marking | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-237938 | (TP for NR_XR_enh BL CR for TS38.423) Support for ECN Marking | Ericsson, Deutsche Telekom, BT, T-Mobile USA, Charter, Vodafone, Apple, Orange, AT&T, Verizon Wireless, Telstra, Qualcomm, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-237966 | (TP for NR_XR_enh BL CR for TS38.473) ECN marking for L4S and congestion monitoring | Huawei, Ericsson, Samsung, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237969 | (TP for TS38.413 BL CR) Support for ECN marking | Nokia, Nokia Shanghai Bell, CMCC, ZTE, Ericsson, LGE, Huawei, Samsung |
| R3-237973 | (TP for TS38.425) Support for ECN marking | CMCC, Nokia, Nokia Shanghai Bell, ZTE |
| 26.1 | eNPN WI | |
| R3-237099 | (BLCR to 29.413) Support of the enhanced NPN phase 2 | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson |
| R3-237100 | (BLCR to 38.300) On introduction of R18 eNPN | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-237101 | (BL CR to 38.413) Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-237102 | (BL CR to 38.423) Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-237465 | (BL CR to 38.423) Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-237759 | (BLCR to 38.300) On introduction of R18 eNPN | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-237799 | (BL CR to 38.413) Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-237825 | (CR to 29.413) Support of the enhanced NPN phase 2 | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson |
| R3-237826 | (CR to 38.300) On introduction of R18 eNPN | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-237827 | (CR to 38.423) Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-237852 | (CR to 38.413) Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| 26.2 | Timing Resiliency and URLLC WI | |
| R3-237103 | (BL CR for TS 38.401) Introduction of 5G Timing Resiliency and URLLC enhancements | Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT, Ericsson, Huawei, ZTE |
| R3-237104 | (BL CR to 38.410) Introduction of 5G Timing Resiliency and URLLC enhancements | Samsung |
| R3-237105 | (BL CR to 38.470) Introduction of 5G Timing Resiliency and URLLC enhancements | China Telecom, ZTE, Huawei, Nokia, Nokia Shanghai Bell |
| R3-237106 | (BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-237107 | (BL CR for TS 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-237108 | (BLCR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-237154 | Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN) | SA2(Nokia) |
| R3-237195 | (TP for TS 38.413 BL CR) Resolution of open issues for TRS and URLLC | Nokia, Nokia Shanghai Bell |
| R3-237196 | (TP for TS 38.473 BL CR) RAN TSS reporting over F1 | Nokia, Nokia Shanghai Bell |
| R3-237231 | (TP to BLCR for TS 38.413, 38.423, 38.473 and 38.401) Support of 5G Timing Resiliency enhancements | Huawei, China Unicom |
| R3-237232 | (TP to BLCR for TS 38.413) Support of RAN feedback enhancements | Huawei, China Unicom |
| R3-237233 | (TP to BLCR for TS 38.413) Support of TSN enabled transport network | Huawei, China Unicom, Ericsson, China Telecommunication |
| R3-237249 | (TP for TS 38.413 BL CR) Interworking with TSN network | Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Ericsson |
| R3-237259 | Discussion on remaining open issues in TSS | Qualcomm Incorporated |
| R3-237501 | Text Proposal to [BL CR for TS 38.423]: Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson |
| R3-237502 | Further discussion on Support NR Timing Resiliency and URLLC enhancements | Ericsson, CATT |
| R3-237598 | TP for 38.300 on Introduction of 5G Timing Resiliency and URLLC enhancements | CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-237599 | Discussion on Adapting downstream and upstream scheduling | CATT |
| R3-237663 | Discussion on remaining issues of NR Timing Resiliency and uRLLC | ZTE |
| R3-237664 | TPs to BLCR of 38.473 and 38.413 on NR Timing Resiliency and uRLLC | ZTE |
| R3-237800 | (BL CR to 38.410) Introduction of 5G Timing Resiliency and URLLC enhancements | Samsung, Nokia, Nokia Shanghai Bell |
| R3-237804 | CB:#R18URLLC | Nokia |
| R3-237923 | (TP for TS 38.413 BL CR) Resolution of TRS_URLLC open issues | Huawei, China Unicom, Ericsson, China Telecommunication, Nokia, Nokia Shanghai Bell |
| R3-237924 | (TP for TS 38.423 BL CR) Resolution of TRS_URLLC open issues | Ericsson |
| R3-237925 | (TP for TS 38.473 BL CR) Resolution of TRS_URLLC open issues | ZTE |
| R3-237926 | (TP for TS 38.413 BL CR) Interworking with TSN network | Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Ericsson, China Telecom |
| R3-237927 | (TP for TS 38.300) Introduction of 5G Timing Resiliency and URLLC enhancements | CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-237928 | (TP for TS 38.401 BL CR) RAN TSS reporting over F1 | Nokia, Nokia Shanghai Bell, China Telecom, Qualcomm Incorporated |
| R3-237929 | [draft] RAN feedback during handover (to SA2) | Huawei |
| R3-237986 | (TP to BLCR for TS 38.473) Support of 5G Timing Resiliency and URLLC enhancements | ZTE, China Telecom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-238033 | Text Proposal to [BL CR for TS 38.423]: Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson |
| R3-238034 | (TP to BLCR for TS 38.473) Support of 5G Timing Resiliency and URLLC enhancements | ZTE, China Telecom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-238036 | TP for 38.300 on Introduction of 5G Timing Resiliency and URLLC enhancements | CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-238037 | (TP for TS 38.401 BL CR) RAN TSS reporting over F1 | Nokia, Nokia Shanghai Bell, China Telecom, Qualcomm Incorporated, Ericsson, ZTE |
| R3-238038 | RAN feedback during handover | RAN3(Huawei) |
| R3-238133 | Introduction of 5G Timing Resiliency and URLLC enhancements | CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-238134 | Introduction of 5G Timing Resiliency and URLLC enhancements | Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT, Ericsson, Huawei, ZTE |
| R3-238135 | Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT, Qualcomm Incorporated |
| R3-238136 | Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-238137 | Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, China Telecom, CATT |
| R3-238167 | Introduction of 5G Timing Resiliency and URLLC enhancements | China Telecom, ZTE, Huawei, Nokia, Nokia Shanghai Bell |
| R3-238168 | Introduction of 5G Timing Resiliency and URLLC enhancements | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| 26.3 | RAN Slicing WI | |
| R3-237109 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, Qualcomm Incorporated, CATT, Orange, China Unicom, Deutsche Telekom, CMCC, Ericsson |
| R3-237110 | (BL CR to 38.300) Enhancement of RAN Slicing for NR | ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-237111 | Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell, ZTE |
| R3-237112 | (BL CR to 38.473) RAN impact on supporting Network Slice Service continuity scenario | CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237247 | (TP to BLCR for TS 38.300) Finalizing the enhanced network slicing phase 3 | Huawei |
| R3-237462 | (TP for TS 38.413 and TS 38.423) Finalization of Network Slice Service Continuity | Nokia, Nokia Shanghai Bell, Orange, CMCC, CATT, Samsung |
| R3-237463 | (TP for TS 38.300 and TS 38.413) Finalization of Partially Allowed NSSAI | Nokia, Nokia Shanghai Bell, Orange |
| R3-237495 | Enhancements to Target NSSAI | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-237496 | (TP for eNS_Ph3-NR-Core for BLCR TS38.413) Target NSSAI Enhancements | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-237497 | LS on the use of Target NSSAI for optimised slice based mobility | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-237498 | Clarifications and Way Forward on Network Slice Service Continuity | Ericsson |
| R3-237570 | Discussion on remaining issues for RAN slicing enhancement | China Telecommunication |
| R3-237600 | TP for 38.423 for supporting alternative S-NSSAI | CATT, Nokia, Nokia Shanghai Bell |
| R3-237608 | Leftover issues for eNS | ZTE |
| R3-237609 | Support for Network Slices with Area of Service not matching TAs | ZTE,China Telecom,CATT |
| R3-237610 | (TP for BL CR to 38.300) Support Slice Area of Service not mapping to existing TA | ZTE,CATT,China Telecom |
| R3-237611 | (TP for BL CR to 38.423) Support Slice Area of Service not mapping to existing TA | ZTE, CATT, China Telecom |
| R3-237641 | Leftover issues on the enhancement of RAN slicing | Samsung, Nokia, Nokia Shanghai Bell |
| R3-237649 | Discussion on remaining open issue for RAN slicing | LG Electronics |
| R3-237650 | (TP to TS 38.413 and 38.423) TP for RAN slicing enhancement | LG Electronics |
| R3-237676 | Discussion on network slice service continuity | CMCC, Nokia, Nokia Shanghai Bell |
| R3-237805 | (TP for BL CR to 38.300) Support Slice Area of Service not mapping to existing TA | ZTE,CATT,China Telecom, CMCC, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-237809 | (TP for TS 38.300) Finalization of Partially Allowed NSSAI | Nokia, Nokia Shanghai Bell, Orange |
| R3-237810 | CB:#R18Slice | ZTE |
| R3-238062 | Enhancement of RAN Slicing for NR | ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, CMCC, China Unicom, CATT |
| R3-238063 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, Qualcomm Incorporated, CATT, Orange, China Unicom, Deutsche Telekom, CMCC, Ericsson |
| R3-238169 | Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell, ZTE, CATT, Huawei, Ericsson |
| R3-238170 | RAN impact on supporting Network Slice Service continuity scenario | CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| 31.1 | Corrections | |
| R3-237220 | (TPs to NCR BL CRs of TS 38.413 and TS 38.300) Correction on NCR authorization | Huawei |
| R3-237248 | Introduction of early capability restriction for Multi-SIM | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson |
| R3-237313 | Discussion on sidelink CA over F1 interface | ZTE Corporation, Sanechips |
| R3-237364 | F1AP enhancement to handle HO involving DRB Release and Add | Nokia, Nokia Shanghai Bell |
| R3-237464 | Correction of Erroneous Mobility Classification | Nokia, Nokia Shanghai Bell |
| R3-237542 | Discussion on addition of UE Rx Tx Time difference in NR UL E-CID | Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel |
| R3-237543 | Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID [UERxTxTD] | Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel |
| R3-237544 | Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID [UERxTxTD] | Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel |
| R3-237556 | Correction of user location information for wireline access | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Orange |
| R3-237691 | Discussion on avoiding unnecessary setup of DRB(s) in indirect data forwarding | Samsung,ZTE,CATT |
| R3-237692 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung, ZTE, CATT |
| R3-237734 | Response to R3-237220 | ZTE |
| R3-237739 | Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID | Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel, Nokia, Nokia Shanghai Bell |
| R3-237740 | Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID [UERxTxTD] | Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel, Nokia, Nokia Shanghai Bell |
| R3-237744 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung, ZTE, CATT, LG Electronics |
| R3-237769 | CB:#13_NRULECID | nn |
| R3-237770 | Introduction of early capability restriction for Multi-SIM | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson |
| R3-237782 | Correction of user location information for wireline access | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Orange |
| R3-237783 | CB:#17_IndirectDataForwarding | Samsung |
| R3-237855 | Introduction of SL CA over F1 interface | ZTE Corporation, Ericsson, Nokia, Nokia Shanghai Bell, Samsung Electronics Co., Ltd, Philips International B.V., CATT, LG Electronics Inc.,China Telecom, Intel Corporation, Qualcomm Inc., Sanechips |
| R3-237950 | Introduction of SL CA over F1 interface | ZTE Corporation, Nokia, Nokia Shanghai Bell, Samsung Electronics Co., Ltd, Philips International B.V., CATT, LG Electronics Inc.,China Telecom, Intel Corporation, Qualcomm Inc., Sanechips |
| R3-237961 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung |
| R3-237968 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung, ZTE, CATT, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
| 31.3 | Endorsed Rel-18 TEI CRs Review | |
| R3-237113 | Location Reporting Enhancements [LRC-Enh] | Ericsson, China Telecom, Huawei, CATT, China Unicom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-237114 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, LG Electronics,China Telecom, Samsung, Ericsson |
| R3-237115 | Switching from SDT to RRC Connected State [Large SDT Uplink Data] | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, ZTE, LG Electronics,China Telecom, Samsung, Ericsson |
| R3-237116 | Correction on Location reporting control [LRC-Enh] | ZTE, Huawei, CATT, China Telecom, China Unicom, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-237117 | Introduction of measurements without gap with interruption | Huawei, Deutsche Telekom, BT |
| R3-237118 | Support of multiple Trace activations | CATT, Huawei, Samsung, ZTE, CMCC |
| R3-237119 | Correction of NG-U | Nokia, Nokia Shanghai Bell |
| R3-237120 | Correction of Transport Addresses | Nokia, Nokia Shanghai Bell, Huawei |
| R3-237121 | Positioning inactive mode for SDT without anchor relocation [POS_SDT] | Huawei, CATT, Samsung, CMCC, ZTE, Ericsson, LG Electronics, Xiaomi, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-237122 | Support of Inactive positioning in SDT without UE context relocation case [POS_SDT] | CATT, Huawei, Ericsson, Samsung, CMCC, ZTE, Xiaomi, LG Electronics, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-237123 | Introduction of 3 MHz channel bandwidth | Ericsson, China Telecom, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237124 | Introduction of 3 MHz channel bandwidth | ZTE,China Telecom, Ericsson,Nokia,Nokia Shanghai Bell |
| R3-237125 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom, ZTE, LG Electronics, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-237126 | Correction on multicast data forwarding in case of UE context retrieval | Huawei, CBN, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Lenovo, Qualcomm Incorporated, CATT, ZTE |
| R3-237127 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Huawei, CBN, Samsung, CMCC, Ericsson, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-237128 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Lenovo, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-237129 | Correction of Paging with PEI | Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson |
| R3-237130 | Correction on SI delivery to RedCap UE | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237131 | Correction for HARQ Related Assistance Information in NR User Plane | Samsung, ZTE, China Telecom, CMCC, Lenovo, Qualcomm |
| R3-237132 | Introduction of new attributes "Resource Coordination Only" in ANR | Ericsson, ZTE, China Telecom, CATT, Huawei |
| R3-237133 | Support of preconfigured Measurement GAP | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, CATT, Huawei, ZTE |
| R3-237134 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, LG Electronics, China Telecom, Samsung, Ericsson |
| R3-237157 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN [ReportAmount_MDT_E-UTRAN] | Huawei, Deutsche Telekom, Orange, Ericsson |
| R3-237158 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN [ReportAmount_MDT_E-UTRAN] | Huawei, Deutsche Telekom, Orange, Ericsson |
| R3-237159 | Support 1-symbol PRS [1symbol_PRS] | ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-237160 | Support 1-symbol PRS [1symbol_PRS] | ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-237763 | Correction on SI delivery to RedCap UE | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-237764 | Support of preconfigured Measurement GAP | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, CATT, Huawei, ZTE |
| R3-237765 | Support of multiple Trace activations | CATT, Huawei, Samsung, ZTE, CMCC, Nokia, Nokia Shanghai Bell |
| R3-237766 | positioning inactive mode for SDT without anchor relocation [POS_SDT] | Huawei, CATT, Samsung, CMCC, ZTE, Ericsson, LG Electronics, Xiaomi, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-237767 | Correction on multicast data forwarding in case of UE context retrieval | Huawei, CBN, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Lenovo, Qualcomm Incorporated, CATT, ZTE |
| R3-237768 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Huawei, CBN, Samsung, CMCC, Ericsson, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |